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.
345  * svc_rdma_encode_read_list - Encode RPC Reply's Read chunk list
346  * @sctxt: Send context for the RPC Reply
349  *   On success, returns length in bytes of the Reply XDR buffer
350  *   that was consumed by the Reply Read list
362  * @sctxt: Send context for the RPC Reply
366  *   On success, returns length in bytes of the Reply XDR buffer
402  * @sctxt: Send context for the RPC Reply
406  * Reply transport header. Update each segment's length field
410  *   On success, returns length in bytes of the Reply XDR buffer
448  * svc_rdma_encode_write_list - Encode RPC Reply's Write chunk list
449  * @rctxt: Reply context with information about the RPC Call
450  * @sctxt: Send context for the RPC Reply
454  * in the segments in the first Write chunk in the Reply's transport
462  *   On success, returns length in bytes of the Reply XDR buffer
463  *   that was consumed by the Reply's Write list
487  * svc_rdma_encode_reply_chunk - Encode RPC Reply's Reply chunk
488  * @rctxt: Reply context with information about the RPC Call
489  * @sctxt: Send context for the RPC Reply
490  * @length: size in bytes of the payload in the Reply chunk
493  * - Reply can always fit in the client-provided Reply chunk
496  *   On success, returns length in bytes of the Reply XDR buffer
497  *   that was consumed by the Reply's Reply chunk
548  * @rctxt: Write and Reply chunks provided by client
597  * svc_rdma_pull_up_reply_msg - Copy Reply into a single buffer
600  * @rctxt: Write and Reply chunks provided by client
603  * The device is not capable of sending the reply directly.
660  * @rctxt: Write and Reply chunks provided by client
684 	/* If there is a Reply chunk, nothing follows the transport  in svc_rdma_map_reply_msg()
769 /* Prepare the portion of the RPC Reply that will be transmitted
773  * Depending on whether a Write list or Reply chunk is present,
778  * RDMA Send is the last step of transmitting an RPC reply. Pages
785  * - The Reply's transport header will never be larger than a page.
816  * Given the client-provided Read, Write, and Reply chunks, the
817  * server was not able to parse the Call or form a complete Reply.
879  * svc_rdma_sendto - Transmit an RPC reply
880  * @rqstp: processed RPC request, reply XDR already in ::rq_res
883  * If no reply message was possible, the connection is closed.
886  *	%0 if an RPC reply has been successfully posted,