Lines Matching refs:messages

18  (*) Control messages.
245  (*) When receiving data or messages for a call, MSG_EOR is flagged by recvmsg
250      Any messages waiting in the receive queue for that call will be discarded.
253      and control data messages will be set to indicate the context.  Receiving
285  (*) If there's a sequence of data messages belonging to a particular call on
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
638      of sendmsg() calls, each with the following control messages attached:
647      control messages attached:
657      control messages attached:
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
755  (*) Intercept received RxRPC messages.
766      All messages that would otherwise wind up in the socket's Rx queue are
768      the messages in the right order to maintain DATA message sequentiality.
787      The two error messages can be probed with rxrpc_kernel_get_error_number().
790      Data messages can have their contents extracted with the usual bunch of
796      Non-data messages should be handled to rxrpc_kernel_free_skb() to dispose
848      messages, but in the former case there will not.