summaryrefslogtreecommitdiffstats
path: root/drivers
diff options
context:
space:
mode:
authorEli Cohen <eli@dev.mellanox.co.il>2008-07-14 23:48:45 -0700
committerRoland Dreier <rolandd@cisco.com>2008-07-14 23:48:45 -0700
commitd1f2cd895f8733faa9d79d09d825a2ed80002ac7 (patch)
tree45d8f35de710b091af17611f3362f82834b5630f /drivers
parente7e55829999deaab3f43e201a087731c02c54cf9 (diff)
downloadop-kernel-dev-d1f2cd895f8733faa9d79d09d825a2ed80002ac7.zip
op-kernel-dev-d1f2cd895f8733faa9d79d09d825a2ed80002ac7.tar.gz
IB/mlx4: Configure QPs' max message size based on real device capability
ConnectX returns the max message size it supports through the QUERY_DEV_CAP firmware command. When modifying a QP to RTR, the max message size for the QP must be specified. This value must not exceed the value declared through QUERY_DEV_CAP. The current code ignores the max allowed size and unconditionally sets the value to 2^31. This patch sets all QPs to the max value allowed as returned from firmware. Signed-off-by: Eli Cohen <eli@mellanox.co.il> Signed-off-by: Roland Dreier <rolandd@cisco.com>
Diffstat (limited to 'drivers')
-rw-r--r--drivers/infiniband/hw/mlx4/qp.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/drivers/infiniband/hw/mlx4/qp.c b/drivers/infiniband/hw/mlx4/qp.c
index 4b0ac5d..76054a7 100644
--- a/drivers/infiniband/hw/mlx4/qp.c
+++ b/drivers/infiniband/hw/mlx4/qp.c
@@ -908,7 +908,8 @@ static int __mlx4_ib_modify_qp(struct ib_qp *ibqp,
attr->path_mtu);
goto out;
}
- context->mtu_msgmax = (attr->path_mtu << 5) | 31;
+ context->mtu_msgmax = (attr->path_mtu << 5) |
+ ilog2(dev->dev->caps.max_msg_sz);
}
if (qp->rq.wqe_cnt)
OpenPOWER on IntegriCloud