[VMM:QUESTION] What's the difference with peek and get?

[cnspy]

try_get vmm

Hi, what's the difference between peek and get of vmm_channel?

I try to use the code like this:

in_chan.peek(tran_data);
do_read(tran_data);
in_chan.get(tran_data);

It works.

But if I try it like this:
in_chan.get(tran_data);
do_read(tran_data);

I think the simulation was blocked. So I don't know why.

 

[telantan]

difference between channel get and peek

in_chan.peek(tran_data);
get a copy of tran_data,the original tran_data still stays in channel

in_chan.get(tran_data);
get the tran_data out from channel and the channel is empty now

 

[cnspy]

peek + channel + vmm

Thanks telantan:

But I think the difference is only the data is move out from the channel or not. Why the simulation will be blocked when using the in_chan.get() only?

Does the get() will copy the data to tran_data?

 

[vishalvartak]

channel peek in vmm

In case, tere is only one data in the channel. Get takes it out from the channel. So nothing remains in the channel. Now get is a blocking task. It will be blocked till another data arrives in teh channel. There would be some non-blocking task as well (Something like can_get or some other name). This non-blocking task will not be blocked in case there is no data in the channel

 

[vinod_cheedella]

blocking get in vmm_channel

.get() will take out the data from the channe,
.peek() will just take the copy of the data,

both the tasks are blocking,
stops simulation unless the channel is again having atleast one data member.

if the channel is empty, and if you are doing .get() on that, obviously simulation will be blocked.

there are non_blocking tasks try_get() and try_peek() which works like get() and peek(), but does't blocks the simulation, if the channel is empty,
simply they returns '0' and continues the simulation further...

 

[cnspy]

how to stop a blocking get vmm

Thanks vishalvartak and vinod_cheedella:

I got where I make the mistake.

Now I have another question. In the program block, I have run the env.run() and I triggered the env.end_test. But the simulation does not stop.