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
283 Notes on sendmsg:
285  (*) MSG_WAITALL can be set to tell sendmsg to ignore signals if the peer is
290      If this isn't set, sendmsg() will return immediately, either returning
327 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:
607      sendmsg() call.
628 first sendmsg() of a call.  The client should then check srx_service in the
630 hold the same value as given to sendmsg() if the upgrade request was ignored by
709  (7) The server then accepts the new call by issuing a sendmsg() with two
728      of sendmsg() calls, each with the following control messages attached:
746      aborted by calling sendmsg() with a dataless message with the following
756 the one server socket, using control messages on sendmsg() and recvmsg() to
811      The user_call_ID is equivalent to that supplied to sendmsg() in the