summaryrefslogtreecommitdiffstats
path: root/net/dccp
diff options
context:
space:
mode:
authorChuck Lever <chuck.lever@oracle.com>2016-11-29 10:52:24 -0500
committerAnna Schumaker <Anna.Schumaker@Netapp.com>2016-11-29 16:45:44 -0500
commit5e9fc6a06bba9e6821ce964067fcf4401496bc29 (patch)
treea6878d11ea8b32ae4b6da2977ecb72b74c6fd9d7 /net/dccp
parent8d38de65644d900199f035277aa5f3da4aa9fc17 (diff)
downloadop-kernel-dev-5e9fc6a06bba9e6821ce964067fcf4401496bc29.zip
op-kernel-dev-5e9fc6a06bba9e6821ce964067fcf4401496bc29.tar.gz
xprtrdma: Support for SG_GAP devices
Some devices (such as the Mellanox CX-4) can register, under a single R_key, a set of memory regions that are not contiguous. When this is done, all the segments in a Reply list, say, can then be invalidated in a single LocalInv Work Request (or via Remote Invalidation, which can invalidate exactly one R_key when completing a Receive). This means a single FastReg WR is used to register, and one or zero LocalInv WRs can invalidate, the memory involved with RDMA transfers on behalf of an RPC. In addition, xprtrdma constructs some Reply chunks from three or more segments. By registering them with SG_GAP, only one segment is needed for the Reply chunk, allowing the whole chunk to be invalidated remotely. Signed-off-by: Chuck Lever <chuck.lever@oracle.com> Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
Diffstat (limited to 'net/dccp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud