Lines Matching refs:message

230  (*) Once the application has received the last message associated with a call,
246      to indicate the terminal message for that call.
248  (*) A call may be aborted by adding an abort control message to the control
254      an abort or a busy message terminates the kernel's use of that call's tag.
267      message to server application to let it know there's a new call awaiting
268      its acceptance [recvmsg reports a special control message].  The server
290      (b) it meets a non-data message,
292      (c) it meets a message belonging to a different call, or
302  (3) If a data message is only partially consumed in filling a user buffer,
303      then the remainder of that message will be left on the front of the queue
307      of the last data message in that phase yet), then MSG_MORE will be
329 	(SRT = usable in Sendmsg / delivered by Recvmsg / Terminal message)
335      message or in the server by passing it in association with an RXRPC_ACCEPT
336      message.  recvmsg() passes it in conjunction with all messages except
337      those of the RXRPC_NEW_CALL message.
355      This is delivered to an application to indicate that an ICMP error message
357      errno-class integer value will be included in the control message data
371      errno-class integer value will be included in the control message data
538      of sendmsg() calls, each with the following control message attached:
547      first request message of that call.
554      All data will be delivered with the following control message attached:
608      it a message for each.  This is received with recvmsg() on the server
609      socket.  It has no data, and has a single dataless control message
615      ignored since the call for which the message was posted may have gone by
633      All data will be delivered with the following control message attached:
642      MSG_MORE should be set in msghdr::msg_flags on all but the last message
646      when it is received.  It will take the form of a dataless message with two
652      MSG_EOR will be flagged to indicate that this is the final message for
656      aborted by calling sendmsg() with a dataless message with the following
753      abort code specified will be placed in the ABORT message sent.
768      the messages in the right order to maintain DATA message sequentiality.
771      and handling the incoming message, the ID assigned by the kernel utility
772      to the call and the socket buffer containing the message.
774      The skb->mark field indicates the type of message:
778 	RXRPC_SKB_MARK_DATA		Data message
786      The remote abort message can be probed with rxrpc_kernel_get_abort_code().
791      socket buffer manipulation functions.  A data message can be determined to
793      data message has been used up, rxrpc_kernel_data_delivered() should be
797      of.  It is possible to get extra refs on all types of message for later
798      freeing, but this may pin the state of a call until the message is finally
820      a BUSY message.  -ENODATA is returned if there were no incoming calls.
824  (*) Record the delivery of a data message and free it.
828      This is used to record a data message as having been delivered and to
831  (*) Free a message.
838  (*) Determine if a data message is the last one on a call.
842      This is used to determine if a socket buffer holds the last data message
846      The data message will be part of the reply on a client call and the
850  (*) Get the abort code from an abort message.
854      This is used to extract the abort code from a remote abort message.
856  (*) Get the error number from a local or network error message.
860      This is used to extract the error number from a message indicating either