Reply with a message
#include <sys/neutrino.h> int MsgReply( int rcvid, int status, const void* msg, int size ); int MsgReply_r( int rcvid, int status, const void* msg, int size );
Use the -l c option to qcc to link against this library. This library is usually included automatically.
The MsgReply() and MsgReply_r() kernel calls reply with a message to the thread identified by rcvid. The thread being replied to must be in the REPLY-blocked state. Any thread in the receiving process is free to reply to the message, however, it may be replied to only once for each receive.
These functions are identical except in the way they indicate errors. See the Returns section for details.
The MsgSend*() in the rcvid thread unblocks with a return value of status.
|The MsgSend*_r() functions return negative errno values to indicate failure, so you shouldn't pass a negative value for the status to MsgReply*(), because the MsgSend*_r() functions could interpret it as an error code.|
The number of bytes transferred is the minimum of that specified by both the replier and the sender. The reply data isn't allowed to overflow the reply buffer area provided by the sender.
The data transfer occurs immediately, and the replying task doesn't block. There's no need to reply to received messages in any particular order, but you must eventually reply to each message to allow the sending thread(s) to continue execution.
None. In the network case, lower priority threads may run.
The MsgReply() function has increased latency when it's used 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 only difference between the MsgReply() and MsgReply_r() functions is the way they indicate errors:
The maximum size for a one-part message-pass is 231 − 1 (SSIZE_MAX).
MsgReceive(), MsgReceivev(), MsgReplyv(), MsgSend(), MsgSendv(), MsgWrite(), MsgWritev()
Message Passing chapter of Getting Started with QNX Neutrino