summaryrefslogtreecommitdiffstats
path: root/Documentation/dvb
diff options
context:
space:
mode:
authorChuck Lever <chuck.lever@oracle.com>2015-01-13 17:03:37 +0100
committerJ. Bruce Fields <bfields@redhat.com>2015-01-15 21:01:47 +0100
commit0b056c224bea63060ce8a981e84193c93fac6f5d (patch)
tree001cbe890f90f8624ae71c6fb0bc19d447896c06 /Documentation/dvb
parentsvcrdma: rc_position sanity checking (diff)
downloadlinux-0b056c224bea63060ce8a981e84193c93fac6f5d.tar.xz
linux-0b056c224bea63060ce8a981e84193c93fac6f5d.zip
svcrdma: Support RDMA_NOMSG requests
Currently the Linux server can not decode RDMA_NOMSG type requests. Operations whose length exceeds the fixed size of RDMA SEND buffers, like large NFSv4 CREATE(NF4LNK) operations, must be conveyed via RDMA_NOMSG. For an RDMA_MSG type request, the client sends the RPC/RDMA, RPC headers, and some or all of the NFS arguments via RDMA SEND. For an RDMA_NOMSG type request, the client sends just the RPC/RDMA header via RDMA SEND. The request's read list contains elements for the entire RPC message, including the RPC header. NFSD expects the RPC/RMDA header and RPC header to be contiguous in page zero of the XDR buffer. Add logic in the RDMA READ path to make the read list contents land where the server prefers, when the incoming message is a type RDMA_NOMSG message. Signed-off-by: Chuck Lever <chuck.lever@oracle.com> Reviewed-by: Steve Wise <swise@opengridcomputing.com> Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'Documentation/dvb')
0 files changed, 0 insertions, 0 deletions