From: Leon Romanovsky <leonro@xxxxxxxxxxxx> The cross-channel feature allows to execute WQEs that involve synchronization of IO operations’ on different QPs. This capability enables to program complex flows with a single function call, hereby significantly reducing overhead associated with IO processing. The queue pairs can be configured to work as a “sync master queue” or “sync slave queues”. 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. * IBV_QP_CREATE_IGNORE_SQ_OVERFLOW configures QP to discard overflow indications on send queue. * IBV_QP_CREATE_IGNORE_RQ_OVERFLOW instructs QP to discard overflow indications on receive queue. Signed-off-by: Leon Romanovsky <leonro@xxxxxxxxxxxx> Reviewed-by: Sagi Grimberg <sagig@xxxxxxxxxxxx> --- include/infiniband/verbs.h | 5 +++++ man/ibv_create_qp_ex.3 | 18 ++++++++++++++++-- src/cmd.c | 5 ++++- 3 files changed, 25 insertions(+), 3 deletions(-) diff --git a/include/infiniband/verbs.h b/include/infiniband/verbs.h index 466d779592bf..7e85de08bfc9 100644 --- a/include/infiniband/verbs.h +++ b/include/infiniband/verbs.h @@ -769,6 +769,11 @@ enum ibv_qp_init_attr_mask { enum ibv_qp_create_flags { IBV_QP_CREATE_BLOCK_SELF_MCAST_LB = 1 << 1, + IBV_QP_CREATE_CROSS_CHANNEL = 1 << 2, + IBV_QP_CREATE_MANAGED_SEND = 1 << 3, + IBV_QP_CREATE_MANAGED_RECV = 1 << 4, + IBV_QP_CREATE_IGNORE_SQ_OVERFLOW = 1 << 5, + IBV_QP_CREATE_IGNORE_RQ_OVERFLOW = 1 << 6 }; struct ibv_qp_init_attr_ex { diff --git a/man/ibv_create_qp_ex.3 b/man/ibv_create_qp_ex.3 index f772a57b4c55..b80a586306c7 100644 --- a/man/ibv_create_qp_ex.3 +++ b/man/ibv_create_qp_ex.3 @@ -1,6 +1,6 @@ .\" -*- nroff -*- .\" -.TH IBV_CREATE_QP_EX 3 2013-06-26 libibverbs "Libibverbs Programmer's Manual" +.TH IBV_CREATE_QP_EX 3 2015-12-27 libibverbs "Libibverbs Programmer's Manual" .SH "NAME" ibv_create_qp_ex, ibv_destroy_qp \- create or destroy a queue pair (QP) .SH "SYNOPSIS" @@ -47,6 +47,16 @@ uint32_t max_recv_sge; /* Requested max number of s/g elements uint32_t max_inline_data;/* Requested max number of data (bytes) that can be posted inline to the SQ, otherwise 0 */ .in -8 }; +.sp +.mf +enum ibv_qp_create_flags { + IBV_QP_CREATE_BLOCK_SELF_MCAST_LB = 1 << 1, + IBV_QP_CREATE_CROSS_CHANNEL = 1 << 2, /* Set QP to work in cross-channel mode */ + IBV_QP_CREATE_MANAGED_SEND = 1 << 3, /* Send work request posted to this QP won't be executed immediately and requires enabling /* + IBV_QP_CREATE_MANAGED_RECV = 1 << 4, /* Receive work request posted to this QP won't be executed immediately and requires enabling */ + IBV_QP_CREATE_IGNORE_SQ_OVERFLOW = 1 << 5, /* Configure QP to discard overflow indications on send queue */ + IBV_QP_CREATE_IGNORE_RQ_OVERFLOW = 1 << 6 /* Configure QP to discard overflow indications on receive queue */ +}; .fi .PP The function @@ -80,4 +90,8 @@ fails if the QP is attached to a multicast group. .BR ibv_query_qp (3) .SH "AUTHORS" .TP -Yishai Hadas <yishaih@xxxxxxxxxxxx> +Yishai Hadas +.RI < yishaih@xxxxxxxxxxxx > +.TP +Leon Romanovsky +.RI < leonro@xxxxxxxxxxxx > diff --git a/src/cmd.c b/src/cmd.c index 675777a8ee5a..ae33491befb4 100644 --- a/src/cmd.c +++ b/src/cmd.c @@ -815,7 +815,10 @@ static void create_qp_handle_resp_common(struct ibv_context *context, } enum { - CREATE_QP_EX2_SUP_CREATE_FLAGS = IBV_QP_CREATE_BLOCK_SELF_MCAST_LB, + CREATE_QP_EX2_SUP_CREATE_FLAGS = IBV_QP_CREATE_BLOCK_SELF_MCAST_LB | + IBV_QP_CREATE_CROSS_CHANNEL | + IBV_QP_CREATE_MANAGED_SEND | + IBV_QP_CREATE_MANAGED_RECV }; int ibv_cmd_create_qp_ex2(struct ibv_context *context, -- 1.7.12.4 -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html