Lines Matching refs:recvmsg
9 of AF_RXRPC family, using sendmsg() and recvmsg() with control data to send and
203 aborted with an appropriate network error passed through recvmsg().
236 is received with a last recvmsg.
241 (#) When receiving data for a call, recvmsg flags MSG_MORE if there's more
244 (#) When receiving data or messages for a call, MSG_EOR is flagged by recvmsg
251 (#) Aborts, busy notifications and challenge packets are delivered by recvmsg,
267 its acceptance [recvmsg reports a special control message]. The server
269 is done, the first part of the request data will be delivered by recvmsg.
294 Notes on recvmsg:
297 the receive queue, then recvmsg will keep working through them until:
307 If recvmsg is called in blocking mode, it will keep sleeping, awaiting the
325 AF_RXRPC makes use of control messages in sendmsg() and recvmsg() to multiplex
351 message. recvmsg() passes it in conjunction with all messages except
357 sendmsg, or it can be delivered by recvmsg to indicate a remote abort was
414 recvmsg() for the service ID actually in use. The operation probed must
615 (6) The reply data will then be posted to the server socket for recvmsg() to
616 pick up. MSG_MORE will be flagged by recvmsg() if there's more reply data
631 msg_name filled in by recvmsg() when collecting the result. srx_service will
692 through recvmsg() when the request data is delivered to userspace.
699 it a message for each. This is received with recvmsg() on the server
705 The address that can be passed back by recvmsg() at this point should be
719 recvmsg() to pick up. At that point, the RxRPC address for the call can
722 Subsequent request data will be posted to the server socket for recvmsg()
743 (10) The final ACK from the client will be posted for retrieval by recvmsg()
768 the one server socket, using control messages on sendmsg() and recvmsg() to
790 (4) Avoid the overhead of using the recvmsg() call. RxRPC messages can be