Write a reply
#include <sys/neutrino.h> int MsgWrite( int rcvid, const void* msg, int size, int offset ); int MsgWrite_r( int rcvid, const void* msg, int size, int offset );
Use the -l c option to qcc to link against this library. This library is usually included automatically.
The MsgWrite() and MsgWrite_r() kernel calls write data to the reply buffer of a thread identified by rcvid. The thread being written to must be in the REPLY-blocked state. Any thread in the receiving process is free to write to the reply message.
These functions are identical except in the way they indicate errors. See the Returns section for details.
You use this function in one of these situations:
To complete a message exchange, you must call MsgReply*(). The reply doesn't need to contain any data. If it does contain data, then the data is always written at offset zero in the destination thread's reply message buffer. This is a convenient way of writing the header once all of the information has been gathered.
A single call to MsgReply*() is always more efficient than calls to MsgWrite() followed by a call to MsgReply*().
None. In the network case, lower priority threads may run.
The MsgWrite() function has increased latency when you use it to communicate across a network — the server is now writing data to its local lsm-qnet.so, which may need to communicate with the client's lsm-qnet.so to actually transfer the data. The server's MsgWrite() call effectively sends a message to the server's lsm-qnet.so to initiate this data transfer.
But since the server's lsm-qnet.so has no way to determine the size of the client's receive data area, the number of bytes reported as having been transferred by the server during its MsgWrite() call might not be accurate — the reported number will instead reflect the number of bytes transferred by the server to its lsm-qnet.so.
The message is buffered in the server side's lsm-qnet.so until the client replies, in order to reduce the number of network transactions.
If you want to determine the size of the sender's reply buffer, set the _NTO_CHF_REPLY_LEN when you call ChannelCreate().
The only difference between the MsgWrite() and MsgWrite_r() functions is the way they indicate errors:
ChannelCreate(), MsgRead(), MsgReadv(), MsgReceive(), MsgReceivev(), MsgReply(), MsgReplyv(), MsgWritev()
Message Passing chapter of Getting Started with QNX Neutrino