aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/hw_random.txt
diff options
context:
space:
mode:
authorTom Tucker <tom@opengridcomputing.com>2008-08-12 15:12:10 -0500
committerTom Tucker <tom@opengridcomputing.com>2008-10-06 14:46:01 -0500
commit146b6df6a537939570c5772ebd7db826fdbd5d82 (patch)
tree1acf55f3244719e543fb5f6eed6de11c5dd3110e /Documentation/hw_random.txt
parent5b180a9a64ca2217a658bd515ef910eafefc5e5a (diff)
downloadkernel_samsung_tuna-146b6df6a537939570c5772ebd7db826fdbd5d82.zip
kernel_samsung_tuna-146b6df6a537939570c5772ebd7db826fdbd5d82.tar.gz
kernel_samsung_tuna-146b6df6a537939570c5772ebd7db826fdbd5d82.tar.bz2
svcrdma: Modify the RPC recv path to use FRMR when available
RPCRDMA requests that specify a read-list are fetched with RDMA_READ. Using an FRMR to map the data sink improves NFSRDMA security on transports that place the RDMA_READ data sink LKEY on the wire because the valid lifetime of the MR is only the duration of the RDMA_READ. The LKEY is invalidated when the last RDMA_READ WR completes. Mapping the data sink also allows for very large amounts to data to be fetched with a single WR, so if the client is also using FRMR, the entire RPC read-list can be fetched with a single WR. Signed-off-by: Tom Tucker <tom@opengridcomputing.com>
Diffstat (limited to 'Documentation/hw_random.txt')
0 files changed, 0 insertions, 0 deletions