summaryrefslogtreecommitdiffstats
path: root/fs/jfs/jfs_btree.h
diff options
context:
space:
mode:
authorSean Hefty <sean.hefty@intel.com>2011-05-23 19:59:25 -0700
committerRoland Dreier <roland@purestorage.com>2011-10-13 09:16:19 -0700
commitb42b63cf0dde2af6eec462b2d6cca7d938702a28 (patch)
treeabb1c06c6903bdc816b5a09a25ea3e4b2bda7842 /fs/jfs/jfs_btree.h
parent418d51307d102e72e745031adb4f5ba0ddb646e2 (diff)
downloadblackbird-op-linux-b42b63cf0dde2af6eec462b2d6cca7d938702a28.tar.gz
blackbird-op-linux-b42b63cf0dde2af6eec462b2d6cca7d938702a28.zip
RDMA/core: Add XRC QPs
XRC ("eXtended reliable connected") is an IB transport that provides better scalability by allowing senders to specify which shared receive queue (SRQ) should be used to receive a message, which essentially allows one transport context (QP connection) to serve multiple destinations (as long as they share an adapter, of course). XRC communication is between an initiator (INI) QP and a target (TGT) QP. Target QPs are associated with SRQs through an XRCD. An XRC TGT QP behaves like a receive-only RD QP. XRC INI QPs behave similarly to RC QPs, except that work requests posted to an XRC INI QP must specify the remote SRQ that is the target of the work request. We define two new QP types for XRC, to distinguish between INI and TGT QPs, and update the core layer to support XRC QPs. This patch is derived from work by Jack Morgenstein <jackm@dev.mellanox.co.il> Signed-off-by: Sean Hefty <sean.hefty@intel.com> Signed-off-by: Roland Dreier <roland@purestorage.com>
Diffstat (limited to 'fs/jfs/jfs_btree.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud