RE: [sv-ec] Strict FIFO ordering of mailboxes try_put/try_get

From: Arturo Salz <Arturo.Salz_at_.....>
Date: Tue Feb 13 2007 - 13:18:22 PST
Dave,

 

I agree with this interpretation. The FIFO ordering is only intended to
be guaranteed for "messages" in the mailbox's internal queue: after a
successful try_put.

 

            Arturo

 

________________________________

From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of
Rich, Dave
Sent: Tuesday, February 13, 2007 8:58 AM
To: sv-ec@eda-stds.org
Subject: RE: [sv-ec] Strict FIFO ordering of mailboxes try_put/try_get

 

I didn't get a response to this. I'm going to go with the assumption
that try_put/try_get can preempt a waiting put/get. 

 

We might want to clarify that strict FIFO order apples only after a
successful try.

 

Dave

 

 

________________________________

From: owner-sv-ec@server.eda.org [mailto:owner-sv-ec@server.eda.org] On
Behalf Of Rich, Dave
Sent: Friday, February 02, 2007 10:48 AM
To: sv-ec@server.eda-stds.org
Subject: [sv-ec] Strict FIFO ordering of mailboxes try_put/try_get

 

This is related to a discussion with semaphores a few years back
http://www.eda-stds.org/sv-ec/hm/2651.html

 

14.3.4 says 

 

The try_put() method stores a message in the mailbox in strict FIFO
order. This method is meaningful

only for bounded mailboxes. If the mailbox is not full, then the
specified message is placed in the mailbox,

and the function returns a positive integer. If the mailbox is full, the
method returns 0.

 

 

Is the strict ordering only with other try_put()'s or if another put()
is blocked waiting for space, must the put() be unblocked before try_put
could succeed? Same question for try_get. Must a waiting get be
unblocked before try_get could succeed?

 

Dave

 

 

David Rich
Verification Technologist
Design Verification & Test Division
Mentor Graphics Corporation
dave_rich@mentor.com
Office:   408 487-7206
Cell:     510 589-2625

 


-- 
This message has been scanned for viruses and 
dangerous content by MailScanner <http://www.mailscanner.info/> , and is

believed to be clean. 
-- 
This message has been scanned for viruses and 
dangerous content by MailScanner <http://www.mailscanner.info/> , and is

believed to be clean. 

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Received on Tue Feb 13 13:18:59 2007

This archive was generated by hypermail 2.1.8 : Tue Feb 13 2007 - 13:19:12 PST