Lines Matching refs:sendmsg
9 of AF_RXRPC family, using sendmsg() and recvmsg() with control data to send and
214 (#) The first sendmsg for a request to be sent from a client contains a tag to
220 first sendmsg() of a call (struct msghdr::msg_name).
226 first sendmsg() of the call must specify the target address. The server's
238 (#) When sending data for a call, sendmsg is given MSG_MORE if there's more
268 application then uses sendmsg to assign a tag to the new call. Once that
282 Notes on sendmsg:
284 (#) MSG_WAITALL can be set to tell sendmsg to ignore signals if the peer is
289 If this isn't set, sendmsg() will return immediately, either returning
325 AF_RXRPC makes use of control messages in sendmsg() and recvmsg() to multiplex
357 sendmsg, or it can be delivered by recvmsg to indicate a remote abort was
401 accepted (it may have timed out, been aborted, etc.), then sendmsg will
429 first sendmsg() providing data for a call. EMSGSIZE will be generated if
586 be done through sendmsg)::
599 of sendmsg() calls, each with the following control message attached:
609 sendmsg() call.
630 first sendmsg() of a call. The client should then check srx_service in the
632 hold the same value as given to sendmsg() if the upgrade request was ignored by
710 (7) The server then accepts the new call by issuing a sendmsg() with two
734 of sendmsg() calls, each with the following control messages attached:
756 aborted by calling sendmsg() with a dataless message with the following
768 the one server socket, using control messages on sendmsg() and recvmsg() to
824 The user_call_ID is equivalent to that supplied to sendmsg() in the