Lines Matching +refs:get +refs:reply
61 receives a blob (the reply), and the server receives the request and then
62 transmits the reply.
127 which the service receives; then the service transmits the reply data
155 (#) Reception of a reply data packet implicitly hard-ACK's all the data
158 (#) An call is complete when the request has been sent, the reply has been
159 received and the final hard-ACK on the last packet of the reply has
212 followed by the reply being received with one or more recvmsgs.
235 the reply is transmitted with one or more sendmsgs, and then the final ACK
578 This issues a request_key() to get the key representing the security
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
635 The caller has to wait until it sees the service ID in the reply before sending
733 (9) The reply data should then be posted to the server socket using a series
755 (11) Up to the point the final packet of reply data is sent, the call can be
791 intercepted before they get put into the socket Rx queue and the socket
880 reply part of a server call. msg.msg_iovlen and msg.msg_iov specify the
904 This is used to receive data from either the reply part of a client call
983 is possible to get extra refs on all types of message for later freeing,
1030 call. It's intended to be used for setting the reply size as the request