Home > Community > Blogs > Functional Verification > performance aware e coding guidelines part 4
 
Login with a Cadence account.
Not a member yet?
Create a permanent login account to make interactions with Cadence more conveniennt.

Register | Membership benefits
Get email delivery of the Functional Verification blog (individual posts).
 

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

Performance-Aware e Coding Guidelines – Part 4

Comments(0)Filed under: Functional Verification, OVM, IES, e, Specman, IEEE 1647, OVM e, IES-XL, tech tips, OVM-e, API, specman elite, performance, sequences

Specman 8.2s3 contains a new API to the sequence driver that enables users to improve the performance of stimulus creation.  With this API you can create stimulus items in an efficient manner, and reduce the number of context switches between the sequence and its driver. For example, instead of many generation actions, you can simply send items from a list:

for each in input_list {
    driver.wait_for_grant(me);
    driver.deliver_item(it);
    driver.wait_for_item_done(me);
};

 

There are many more use models of the Sequences API, and you’ll find many detailed examples in the OVM User Guide.

Until the next & final segment of the series (where I’ll discuss Temporals), happy coding!

Efrat Shneydor
Methodology R&D


Reference links to prior posts in this series: 
Part 1 – Improving the performance of Lists
Part 2 – Memory savings from proper Base types extensions and using CONST fields
Part 3 – Knowing when to turn off the Generator

Comments(0)

Leave a Comment


Name
E-mail (will not be published)
Comment
 I have read and agree to the Terms of use and Community Guidelines.
Community Guidelines
The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.