Lines Matching full:reply

48  * RPC server when an RPC Reply is ready to be transmitted to a client.
51  * XDR-encoded RPC Reply message. sendto must construct the RPC-over-RDMA
52  * transport header, post all Write WRs needed for this Reply, then post
56  * svc_rdma_sendto must fully transmit the Reply before returning, as
64  * The I/O that performs Reply transmission is asynchronous, and may
79  * The ownership of all of the Reply's pages are transferred into that
83  * Send completion handler finally releases the Reply's pages.
94  *   handler releases the Reply's pages.
96  *   the Reply's pages.
394  * svc_rdma_encode_read_list - Encode RPC Reply's Read chunk list
395  * @sctxt: Send context for the RPC Reply
398  *   On success, returns length in bytes of the Reply XDR buffer
399  *   that was consumed by the Reply Read list
410  * @sctxt: Send context for the RPC Reply
416  *   On success, returns length in bytes of the Reply XDR buffer
444  * @sctxt: Send context for the RPC Reply
448  * Reply transport header. Update each segment's length field
452  *   On success, returns length in bytes of the Reply XDR buffer
485  * svc_rdma_encode_write_list - Encode RPC Reply's Write chunk list
486  * @rctxt: Reply context with information about the RPC Call
487  * @sctxt: Send context for the RPC Reply
490  *   On success, returns length in bytes of the Reply XDR buffer
491  *   that was consumed by the Reply's Write list
517  * svc_rdma_encode_reply_chunk - Encode RPC Reply's Reply chunk
518  * @rctxt: Reply context with information about the RPC Call
519  * @sctxt: Send context for the RPC Reply
520  * @length: size in bytes of the payload in the Reply chunk
523  *   On success, returns length in bytes of the Reply XDR buffer
524  *   that was consumed by the Reply's Reply chunk
526  *   %-E2BIG if the RPC message is larger than the Reply chunk
768  * svc_rdma_pull_up_reply_msg - Copy Reply into a single buffer
774  * The device is not capable of sending the reply directly.
808  * @reply_pcl: Reply chunk provided by client
833 	/* If there is a Reply chunk, nothing follows the transport  in svc_rdma_map_reply_msg()
868 /* Prepare the portion of the RPC Reply that will be transmitted
872  * Depending on whether a Write list or Reply chunk is present,
878  * - The Reply's transport header will never be larger than a page.
915  * Given the client-provided Read, Write, and Reply chunks, the
916  * server was not able to parse the Call or form a complete Reply.
978  * svc_rdma_sendto - Transmit an RPC reply
979  * @rqstp: processed RPC request, reply XDR already in ::rq_res
982  * If no reply message was possible, the connection is closed.
985  *	%0 if an RPC reply has been successfully posted,