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

 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 

Parents

  • I will assume you are referring to eRM or OVM generation of transactions.

    Push mode (recommended by other methodologies) refers to the generator creating transactions and pushing them to the BFM or Driver which then uses the transaction to drive the DUT. This has a problem that the generator is creating transactions before the driver requests them and therefore might not reflect constraints that the test is requiring, i.e. not reactive. This results in the possibility that those transactions will be discarded and new transactions having to being generated.

    Pull mode refers to the generator creating transactions in response to the driver requesting them. This is more efficient in that the driver can add additional constraints before requesting the transaction and therefore get only the transactions needed. This is recommended and built-in to eRM/OVM.

    Tim

Reply

  • I will assume you are referring to eRM or OVM generation of transactions.

    Push mode (recommended by other methodologies) refers to the generator creating transactions and pushing them to the BFM or Driver which then uses the transaction to drive the DUT. This has a problem that the generator is creating transactions before the driver requests them and therefore might not reflect constraints that the test is requiring, i.e. not reactive. This results in the possibility that those transactions will be discarded and new transactions having to being generated.

    Pull mode refers to the generator creating transactions in response to the driver requesting them. This is more efficient in that the driver can add additional constraints before requesting the transaction and therefore get only the transactions needed. This is recommended and built-in to eRM/OVM.

    Tim

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.