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.
363 * svc_rdma_encode_read_list - Encode RPC Reply's Read chunk list
364 * @sctxt: Send context for the RPC Reply
367 * On success, returns length in bytes of the Reply XDR buffer
368 * that was consumed by the Reply Read list
379 * @sctxt: Send context for the RPC Reply
385 * On success, returns length in bytes of the Reply XDR buffer
413 * @sctxt: Send context for the RPC Reply
417 * Reply transport header. Update each segment's length field
421 * On success, returns length in bytes of the Reply XDR buffer
454 * svc_rdma_encode_write_list - Encode RPC Reply's Write chunk list
455 * @rctxt: Reply context with information about the RPC Call
456 * @sctxt: Send context for the RPC Reply
459 * On success, returns length in bytes of the Reply XDR buffer
460 * that was consumed by the Reply's Write list
486 * svc_rdma_encode_reply_chunk - Encode RPC Reply's Reply chunk
487 * @rctxt: Reply context with information about the RPC Call
488 * @sctxt: Send context for the RPC Reply
489 * @length: size in bytes of the payload in the Reply chunk
492 * On success, returns length in bytes of the Reply XDR buffer
493 * that was consumed by the Reply's Reply chunk
495 * %-E2BIG if the RPC message is larger than the Reply chunk
737 * svc_rdma_pull_up_reply_msg - Copy Reply into a single buffer
743 * The device is not capable of sending the reply directly.
777 * @reply_pcl: Reply chunk provided by client
802 /* If there is a Reply chunk, nothing follows the transport in svc_rdma_map_reply_msg()
837 /* Prepare the portion of the RPC Reply that will be transmitted
841 * Depending on whether a Write list or Reply chunk is present,
846 * RDMA Send is the last step of transmitting an RPC reply. Pages
853 * - The Reply's transport header will never be larger than a page.
886 * Given the client-provided Read, Write, and Reply chunks, the
887 * server was not able to parse the Call or form a complete Reply.
949 * svc_rdma_sendto - Transmit an RPC reply
950 * @rqstp: processed RPC request, reply XDR already in ::rq_res
953 * If no reply message was possible, the connection is closed.
956 * %0 if an RPC reply has been successfully posted,