• 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. pull mode vs push mode

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 67
  • Views 18500
  • 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

pull mode vs push mode

onkarkk
onkarkk over 16 years ago

 Hi,

Could any help me out in understanding the difference between pull mode and push mode . I am really not understanding this theory . please help me out.

Thanks in advance,

regards,

Krishna Kishore 

  • Cancel
Parents
  • Efrat
    Efrat over 14 years ago
    hi, The main issue here is when does the sequence driver picks the next "do". In Pull mode, this decision is made right before injecting the item. In Push mode - this decision might be made many cycles before the injection. Consider, for example, the case when the driver picks the next "do" from sequence A. Cycles passes, and in the mean time - seq B proceeds (perhaps it was waiting for some event), and now it grabs the driver. But the driver already picked another "do", not the B's. This results with a scenario not matching user's intention. While developing layered sequences examples (some are included in uvm/uvm_examples), we came to realize several use models when Push mode just wouldn't work (or - more accurate - requires too much user code). Because in layered sequences, there is a delicate synchronization between high layer, low layer, their drivers and BFMs. To your question - we came to conclusion that Pull mode is the recommended mode. We yet have not seen a use model where Push is preferred.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Efrat
    Efrat over 14 years ago
    hi, The main issue here is when does the sequence driver picks the next "do". In Pull mode, this decision is made right before injecting the item. In Push mode - this decision might be made many cycles before the injection. Consider, for example, the case when the driver picks the next "do" from sequence A. Cycles passes, and in the mean time - seq B proceeds (perhaps it was waiting for some event), and now it grabs the driver. But the driver already picked another "do", not the B's. This results with a scenario not matching user's intention. While developing layered sequences examples (some are included in uvm/uvm_examples), we came to realize several use models when Push mode just wouldn't work (or - more accurate - requires too much user code). Because in layered sequences, there is a delicate synchronization between high layer, low layer, their drivers and BFMs. To your question - we came to conclusion that Pull mode is the recommended mode. We yet have not seen a use model where Push is preferred.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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