Lines Matching refs:sendmsg

7 of AF_RXRPC family, using sendmsg() and recvmsg() with control data to send and
215  (*) The first sendmsg for a request to be sent from a client contains a tag to
221      first sendmsg() of a call (struct msghdr::msg_name).
227      first sendmsg() of the call must specify the target address.  The server's
239  (*) When sending data for a call, sendmsg is given MSG_MORE if there's more
269      application then uses sendmsg to assign a tag to the new call.  Once that
315 AF_RXRPC makes use of control messages in sendmsg() and recvmsg() to multiplex
342      sendmsg, or it can be delivered by recvmsg to indicate a remote abort was
386      accepted (it may have timed out, been aborted, etc.), then sendmsg will
525      be done through sendmsg):
538      of sendmsg() calls, each with the following control message attached:
619  (5) The server then accepts the new call by issuing a sendmsg() with two
638      of sendmsg() calls, each with the following control messages attached:
656      aborted by calling sendmsg() with a dataless message with the following
666 the one server socket, using control messages on sendmsg() and recvmsg() to
718      The user_call_ID is equivalent to that supplied to sendmsg() in the