78147ca8b4
This simple data structure binds the location of each data payload inside of an RPC message to the chunk that will be used to push it to or pull it from the client. There are several benefits to this small additional overhead: * It enables support for more than one chunk in incoming Read and Write lists. * It translates the version-specific on-the-wire format into a generic in-memory structure, enabling support for multiple versions of the RPC/RDMA transport protocol. * It enables the server to re-organize a chunk list if it needs to adjust where Read chunk data lands in server memory without altering the contents of the XDR-encoded Receive buffer. Construction of these lists is done while sanity checking each incoming RPC/RDMA header. Subsequent patches will make use of the generated data structures. Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
9 lines
329 B
Makefile
9 lines
329 B
Makefile
# SPDX-License-Identifier: GPL-2.0
|
|
obj-$(CONFIG_SUNRPC_XPRT_RDMA) += rpcrdma.o
|
|
|
|
rpcrdma-y := transport.o rpc_rdma.o verbs.o frwr_ops.o \
|
|
svc_rdma.o svc_rdma_backchannel.o svc_rdma_transport.o \
|
|
svc_rdma_sendto.o svc_rdma_recvfrom.o svc_rdma_rw.o \
|
|
svc_rdma_pcl.o module.o
|
|
rpcrdma-$(CONFIG_SUNRPC_BACKCHANNEL) += backchannel.o
|