Lines Matching refs:message
20 syscalls have to be issued by user-space to get more message.
57 Conversion of the transmit path involves changing message construction to
126 meta-data, and the message itself.
128 Frame: [ header message ]
145 - nm_len contains the length of the message contained in the data area
147 - nm_group specified the destination multicast group of message
156 RX ring: frame belongs to the kernel and contains no message
161 message construction.
164 RX ring only: frame is currently used by the kernel for message
165 construction and contains no valid message yet.
170 RX ring: frame contains a valid message. Approriate action is
171 to process the message and release the frame back to
176 TX ring: the frame contains a valid message from user-space to
182 RX ring only: a message is ready to be processed but could not be
186 to invoke recvmsg() to receive the message and release
191 RX ring only: user-space queued the message for later processing, but
202 As of Jan 2015 the message is always copied from the ring frame to an
275 /* Release empty message immediately. May happen
276 * on error during message construction.
303 A single message is constructed and transmitted, to send multiple messages
321 /* Build message */