# UVM pipelined driver cookbook

**URL:** <https://verificationacademy.com/forums/t/uvm-pipelined-driver-cookbook/38912>\
**Category:** UVM\
**Tags:** UVM\
**Created:** [March 28, 2021, 4:08pm UTC](https://verificationacademy.com/forums/t/uvm-pipelined-driver-cookbook/38912 "2021-03-28T16:08:50Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![harsh\_pandya](https://verificationacademy.com/forums/user_avatar/verificationacademy.com/harsh_pandya/32/2973_2.png) [@harsh\_pandya](https://verificationacademy.com/forums/u/harsh_pandya)\
**Post date:** [March 30, 2021, 4:22am UTC](https://verificationacademy.com/forums/t/uvm-pipelined-driver-cookbook/38912/4 "2021-03-30T04:22:43Z")

</div>

_In reply to [rag123](https://verificationacademy.com/forums/t/uvm-pipelined-driver-cookbook/38912/3):_  
Your understanding is correct in case when we are using get\_next\_item inside driver.  
It is blocked until item\_done or put(rsp).  
But, get is non blocking. So, it is possible you get new seq\_item.  
Please, see below link.  
[https://verificationacademy.com/forums/uvm/difference-between-getnextitem-and-get#:~:text=get\_next\_item()%20is%20a%20blocking,of%20get()%2Fput()](https://verificationacademy.com/forums/uvm/difference-between-getnextitem-and-get#:~:text=get_next_item()%20is%20a%20blocking,of%20get()%2Fput())

Thanks,  
Harsh

---

_[View the full topic](https://verificationacademy.com/forums/t/uvm-pipelined-driver-cookbook/38912)._