diff options
| author | Steve Wise <swise@opengridcomputing.com> | 2007-11-09 09:21:58 -0600 |
|---|---|---|
| committer | Roland Dreier <rolandd@cisco.com> | 2007-11-13 15:27:00 -0800 |
| commit | 9a7666494bac60b99d2bd7d904bd22e8c9b1e3f7 (patch) | |
| tree | a224be9961ef75b43f67d78975df7301bd010a10 /drivers/infiniband | |
| parent | 51aaa54eb9e9f01878aa5d62277fd156e458dfe1 (diff) | |
| download | kernel_samsung_tuna-9a7666494bac60b99d2bd7d904bd22e8c9b1e3f7.zip kernel_samsung_tuna-9a7666494bac60b99d2bd7d904bd22e8c9b1e3f7.tar.gz kernel_samsung_tuna-9a7666494bac60b99d2bd7d904bd22e8c9b1e3f7.tar.bz2 | |
RDMA/cxgb3: Set the max_qp_init_rd_atom attribute in query_device
The device attribute max_qp_init_rd_atom is not getting set in cxgb3's
query_device method. Version 1.0.4 of librdmacm now validates the
user's requested initiator and responder resources against the max
supported by the device. Since iw_cxgb3 wasn't setting this attribute
(and it defaulted to 0), all rdma_connect()s fail if there are
initiator resources requested by the app. Fix this by setting the
correct value in iwch_query_device().
Signed-off-by: Steve Wise <swise@opengridcomputing.com>
Signed-off-by: Roland Dreier <rolandd@cisco.com>
Diffstat (limited to 'drivers/infiniband')
| -rw-r--r-- | drivers/infiniband/hw/cxgb3/iwch_provider.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/infiniband/hw/cxgb3/iwch_provider.c b/drivers/infiniband/hw/cxgb3/iwch_provider.c index f0c7775..b5436ca 100644 --- a/drivers/infiniband/hw/cxgb3/iwch_provider.c +++ b/drivers/infiniband/hw/cxgb3/iwch_provider.c @@ -1000,6 +1000,7 @@ static int iwch_query_device(struct ib_device *ibdev, props->max_sge = dev->attr.max_sge_per_wr; props->max_sge_rd = 1; props->max_qp_rd_atom = dev->attr.max_rdma_reads_per_qp; + props->max_qp_init_rd_atom = dev->attr.max_rdma_reads_per_qp; props->max_cq = dev->attr.max_cqs; props->max_cqe = dev->attr.max_cqes_per_cq; props->max_mr = dev->attr.max_mem_regs; |