Message Passing: Difference between revisions
Jump to navigation
Jump to search
| [unchecked revision] | [unchecked revision] |
Content added Content deleted
No edit summary |
m (Minor spelling fix..) |
||
| Line 26: | Line 26: | ||
==Variable or Fixed Messages Size== |
==Variable or Fixed Messages Size== |
||
A message typically includes the ID of the emitting thread (or a replying port), a message code and a few arguments. Message |
A message typically includes the ID of the emitting thread (or a replying port), a message code and a few arguments. Message queueing and dispatching code can be greatly simplified if message size is fixed. |
||
When messages longer than the fixed-size are required, one will need to provide a way to describe the long message in the small structure. If copying a 4-word message forth and back doesn't imply excessive processing cost, it will be very different for the 1MB of data you send to a disk server. In that case, it is suggested to toy with paging in order to map the real data from the emitter to the receiver's address space. |
When messages longer than the fixed-size are required, one will need to provide a way to describe the long message in the small structure. If copying a 4-word message forth and back doesn't imply excessive processing cost, it will be very different for the 1MB of data you send to a disk server. In that case, it is suggested to toy with paging in order to map the real data from the emitter to the receiver's address space. |
||
| Line 33: | Line 33: | ||
===Forum=== |
===Forum=== |
||
*[[Topic:10116|passing messages through registers]] |
*[[Topic:10116|passing messages through registers]] |
||
*[[Topic:10922|RPC message size, handling |
*[[Topic:10922|RPC message size, handling over sized messages]] |
||
==External Links== |
==External Links== |
||
*[[Wikipedia:Message Passing]] |
*[[Wikipedia:Message Passing]] |
||