svc_rdma_pull_up_reply_msg(9)

🎀 NAME 🎀

okay so this is the svc_rdma_pull_up_reply_msg(9) Kernel API Manual page, and the name is svc_rdma_pull_up_reply_msg — Copy Reply into a single buffer. That's the whole name section and it's lowkey iconic. 💅

✨ SYNOPSIS ✨

       int svc_rdma_pull_up_reply_msg (const struct svcxprt_rdma *rdma , struct
       svc_rdma_send_ctxt *sctxt , const struct svc_rdma_pcl *write_pcl , const
       struct xdr_buf *xdr );

🫶 ARGUMENTS 🫶

• rdma — the controlling transport. it's giving boss of the RDMA situation.
• sctxt — send_ctxt for the Send WR; xprt hdr is already prepared. so don't worry about that part.
• write_pcl — Write chunk list provided by client. ty bestie client.
• xdr — prepared xdr_buf containing RPC message.

💅 DESCRIPTION 💅

The device is not capable of sending the reply directly. like, it literally cannot. So we assemble the elements of xdr into the transport header buffer.

Assumptions: check_pull_up has determined that xdr will fit in the buffer. no cap, that check is doing the pre-work so this function can vibe.

🌈 RETURN 🌈

• 0 — if pull-up was successful. slay. ✨
• -EMSGSIZE — if a buffer manipulation problem occurred. 😭

🔥 SEE ALSO 🔥

Kernel file: ./net/sunrpc/xprtrdma/svc_rdma_sendto.c

• svc_rdma_send_ctxts_destroy(9)
• svc_rdma_send_ctxt_get(9)
• svc_rdma_send_ctxts_drain(9)
• svc_rdma_send_ctxt_put(9)
• svc_rdma_wake_send_waiters(9)
• svc_rdma_sq_wait(9)
• svc_rdma_post_send_err(9)
• svc_rdma_wc_send(9)
• svc_rdma_post_send(9)
• svc_rdma_encode_read_list(9)
• svc_rdma_encode_write_segment(9)
• svc_rdma_encode_write_chunk(9)
• svc_rdma_encode_write_list(9)
• svc_rdma_encode_reply_chunk(9)
• svc_rdma_page_dma_map(9)
• svc_rdma_iov_dma_map(9)
• svc_rdma_xb_dma_map(9)
• svc_rdma_xb_count_sges(9)
• svc_rdma_check_pull_up(9)
• svc_rdma_xb_linearize(9)
• svc_rdma_send_error_msg(9)
• svc_rdma_sendto(9)
• svc_rdma_result_payload(9)

okay byeee 💖 — source/version: ./net/sunrpc/xprtrdma, date: October 2026, page: svc_rdma_pull_up_reply_msg(9). mwah 🫶