Lines Matching refs:recvmsg

7 of AF_RXRPC family, using sendmsg() and recvmsg() with control data to send and
204      aborted with an appropriate network error passed through recvmsg().
237      is received with a last recvmsg.
242  (*) When receiving data for a call, recvmsg flags MSG_MORE if there's more
245  (*) When receiving data or messages for a call, MSG_EOR is flagged by recvmsg
252  (*) Aborts, busy notifications and challenge packets are delivered by recvmsg,
268      its acceptance [recvmsg reports a special control message].  The server
270      is done, the first part of the request data will be delivered by recvmsg.
283 Notes on recvmsg:
286      the receive queue, then recvmsg will keep working through them until:
296      If recvmsg is called in blocking mode, it will keep sleeping, awaiting the
315 AF_RXRPC makes use of control messages in sendmsg() and recvmsg() to multiplex
336      message.  recvmsg() passes it in conjunction with all messages except
342      sendmsg, or it can be delivered by recvmsg to indicate a remote abort was
549  (6) The reply data will then be posted to the server socket for recvmsg() to
550      pick up.  MSG_MORE will be flagged by recvmsg() if there's more reply data
608      it a message for each.  This is received with recvmsg() on the server
614      The address that can be passed back by recvmsg() at this point should be
626      recvmsg() to pick up.  At that point, the RxRPC address for the call can
629      Subsequent request data will be posted to the server socket for recvmsg()
645  (9) The final ACK from the client will be posted for retrieval by recvmsg()
666 the one server socket, using control messages on sendmsg() and recvmsg() to
689  (4) Avoid the overhead of using the recvmsg() call.  RxRPC messages can be