From: Kamal Heib <kamalheib1@gmail.com>
To: linux-rdma@vger.kernel.org
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
Doug Ledford <dledford@redhat.com>,
Kamal Heib <kamalheib1@gmail.com>,
Potnuri Bharat Teja <bharat@chelsio.com>
Subject: [PATCH for-next 3/5] RDMA/cxgb4: Set max_pkeys attribute
Date: Mon, 6 Jul 2020 10:54:17 +0300 [thread overview]
Message-ID: <20200706075419.361484-4-kamalheib1@gmail.com> (raw)
In-Reply-To: <20200706075419.361484-1-kamalheib1@gmail.com>
Make sure to set the max_pkeys attribute to indicate the maximum number
of partitions supported by the cxgb4 device.
Fixes: cfdda9d76436 ("RDMA/cxgb4: Add driver for Chelsio T4 RNIC")
Signed-off-by: Kamal Heib <kamalheib1@gmail.com>
Cc: Potnuri Bharat Teja <bharat@chelsio.com>
---
drivers/infiniband/hw/cxgb4/provider.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/infiniband/hw/cxgb4/provider.c b/drivers/infiniband/hw/cxgb4/provider.c
index 1d3ff59e4060..275b77234a22 100644
--- a/drivers/infiniband/hw/cxgb4/provider.c
+++ b/drivers/infiniband/hw/cxgb4/provider.c
@@ -298,6 +298,7 @@ static int c4iw_query_device(struct ib_device *ibdev, struct ib_device_attr *pro
props->local_ca_ack_delay = 0;
props->max_fast_reg_page_list_len =
t4_max_fr_depth(dev->rdev.lldi.ulptx_memwrite_dsgl && use_dsgl);
+ props->max_pkeys = 1;
return 0;
}
--
2.25.4
next prev parent reply other threads:[~2020-07-06 7:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 7:54 [PATCH for-next 0/5] RDMA/providers: Set max_pkey attribute Kamal Heib
2020-07-06 7:54 ` [PATCH for-next 1/5] RDMA/siw: Set max_pkeys attribute Kamal Heib
2020-07-06 7:54 ` [PATCH for-next 2/5] RDMA/efa: " Kamal Heib
2020-07-06 7:58 ` Gal Pressman
2020-07-06 8:16 ` Kamal Heib
2020-07-06 7:54 ` Kamal Heib [this message]
2020-07-06 7:54 ` [PATCH for-next 4/5] RDMA/i40iw: " Kamal Heib
2020-07-06 7:54 ` [PATCH for-next 5/5] RDMA/usnic: Fix reported " Kamal Heib
2020-07-06 9:06 ` [PATCH for-next 0/5] RDMA/providers: Set max_pkey attribute Kamal Heib
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200706075419.361484-4-kamalheib1@gmail.com \
--to=kamalheib1@gmail.com \
--cc=bharat@chelsio.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).