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.
354  * svc_rdma_encode_read_list - Encode RPC Reply's Read chunk list
355  * @sctxt: Send context for the RPC Reply
358  *   On success, returns length in bytes of the Reply XDR buffer
359  *   that was consumed by the Reply Read list
370  * @sctxt: Send context for the RPC Reply
376  *   On success, returns length in bytes of the Reply XDR buffer
404  * @sctxt: Send context for the RPC Reply
408  * Reply transport header. Update each segment's length field
412  *   On success, returns length in bytes of the Reply XDR buffer
445  * svc_rdma_encode_write_list - Encode RPC Reply's Write chunk list
446  * @rctxt: Reply context with information about the RPC Call
447  * @sctxt: Send context for the RPC Reply
450  *   On success, returns length in bytes of the Reply XDR buffer
451  *   that was consumed by the Reply's Write list
477  * svc_rdma_encode_reply_chunk - Encode RPC Reply's Reply chunk
478  * @rctxt: Reply context with information about the RPC Call
479  * @sctxt: Send context for the RPC Reply
480  * @length: size in bytes of the payload in the Reply chunk
483  *   On success, returns length in bytes of the Reply XDR buffer
484  *   that was consumed by the Reply's Reply chunk
486  *   %-E2BIG if the RPC message is larger than the Reply chunk
656  * @rctxt: Write and Reply chunks provided by client
728  * svc_rdma_pull_up_reply_msg - Copy Reply into a single buffer
731  * @rctxt: Write and Reply chunks provided by client
734  * The device is not capable of sending the reply directly.
767  * @rctxt: Write and Reply chunks provided by client
791 	/* If there is a Reply chunk, nothing follows the transport  in svc_rdma_map_reply_msg()
826 /* Prepare the portion of the RPC Reply that will be transmitted
830  * Depending on whether a Write list or Reply chunk is present,
835  * RDMA Send is the last step of transmitting an RPC reply. Pages
842  * - The Reply's transport header will never be larger than a page.
874  * Given the client-provided Read, Write, and Reply chunks, the
875  * server was not able to parse the Call or form a complete Reply.
937  * svc_rdma_sendto - Transmit an RPC reply
938  * @rqstp: processed RPC request, reply XDR already in ::rq_res
941  * If no reply message was possible, the connection is closed.
944  *	%0 if an RPC reply has been successfully posted,