summaryrefslogtreecommitdiff
path: root/arch/metag/tbx
diff options
context:
space:
mode:
authorLeon Romanovsky <leonro@mellanox.com>2015-12-20 12:16:10 +0200
committerDoug Ledford <dledford@redhat.com>2015-12-23 23:33:14 -0500
commit8a06ce59a4cd034c52c59c44ff6b0785a3969409 (patch)
tree6b42a1d753696101ea2de9d96e3b95119db076e4 /arch/metag/tbx
parent7ca0bc53652382529b1cc1c39987cf93084d5828 (diff)
IB/core: Add cross-channel support
The cross-channel feature allows to execute WQEs that involve synchronization of I/O operations’ on different QPs. This capability enables to program complex flows with a single function call, hereby significantly reducing overhead associated with I/O processing. Cross-channel operations support is indicated by HCA capability information. The queue pairs can be configured to work as a “sync master queue” or “sync slave queues”. The added flags are: 1. Device capability flag IB_DEVICE_CROSS_CHANNEL for the devices that can perform cross-channel operations. 2. CQ property flag IB_CQ_FLAGS_IGNORE_OVERRUN to disable CQ overrun check. This check is useless in cross-channel scenario. 3. QP property flags to indicate if queues are slave or master: * IB_QP_CREATE_MANAGED_SEND indicates that posted send work requests will not be executed immediately and requires enabling. * IB_QP_CREATE_MANAGED_RECV indicates that posted receive work requests will not be executed immediately and requires enabling. * IB_QP_CREATE_CROSS_CHANNEL declares the QP to work in cross-channel mode. If IB_QP_CREATE_MANAGED_SEND and IB_QP_CREATE_MANAGED_RECV are not provided, this QP will be sync master queue, else it will be sync slave. Reviewed-by: Sagi Grimberg <sagig@mellanox.com> Signed-off-by: Leon Romanovsky <leonro@mellanox.com> Signed-off-by: Doug Ledford <dledford@redhat.com>
Diffstat (limited to 'arch/metag/tbx')
0 files changed, 0 insertions, 0 deletions