Message channels fire-and-forget semantics

49 views
Skip to first unread message

aclassifier

unread,
Mar 26, 2012, 7:28:26 AM3/26/12
to
Hi

The "Message Channels" of VxWork document [1] lists these Messaging
modes:
1. Unidirectional send (“fire-and-forget”)
2. Send with asynchronous reply
3. Blocking send-receive-reply (RPC semantics)

Q1. 2-3 would never overflow any buffer pool(?) (one in one out?).
Right?

Q2.1. How will fire-and-forget behave on a fast producer slow consumer
system?

Q2.2. What happens when the buffer pool is full? Crash and restart or
some kind of error handling at application level?

Q2.3. If the system survives, how is the full buffer treated?

Q2.4. Are there any side effects to other tasks? Like, is it like a
"buffered channel" (with channel dimension defined), or will all the
channels share the same buffer pool?

Q3. Are there any restrictions as to sending pointers to shared data
between threads?

Q4. Where would I find this information?

[1] http://www.windriverevents.de/user/Optimize_your_development_with_VxWorks_6.3.pdf

Øyvind Teig
Trondheim Norway

aclassifier

unread,
Mar 28, 2012, 3:25:19 PM3/28/12
to
I try to discuss a little about this at http://oyvteig.blogspot.com/2012/01/038-concurrent-programming-paradigms.html (aclassifier)
Reply all
Reply to author
Forward
0 new messages