• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification
  3. How frequently should Transactor work?

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 64
  • Views 13238
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How frequently should Transactor work?

archive
archive over 18 years ago

Hi all,

I am always confused with the how frequently should transactor is triggered to work.

For instance, there is a transactor XACTOR_A get a transaction from transactor XACTOR_B, and there is a Mailbox containing transactions connecting these two transactors.

I always using the following simple methods. XACTOR_A check if the Mailbox is not empty every clock (i.e. @posedge clk). If the Mailbox is not empty, XACTOR_A get the transaction from it and run its work sequentially.

When using the upper method, I feel the transactor work on physical layer(because it work depend on clock, and was triggered every clock cycle).

Is there any intuitive explanation about how frequently should Transactor work(especially in CDNS's uRM or SNPS's VMM or MENT's AVM)? Any suggestions will appreciated!

Best regards,
Davy


Originally posted in cdnusers.org by davyzhu
  • Cancel
  • archive
    archive over 18 years ago

    If you use mailbox.get(), that will block until there is data in the mailbox.

    Example:
    mailbox mbox = new();
    always begin
    xactor = mbox.get();
    do_something(xactor);
    end

    The always block will call get() and return a value for xactor and send it to do_something. However, if there is nothing in mbox, then it will stop and wait until there is a put() called from XACTOR_B.

    Tim


    Originally posted in cdnusers.org by tpylant
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information