From: Leon Romanovsky <leon@kernel.org>
To: "Håkon Bugge" <haakon.bugge@oracle.com>
Cc: Doug Ledford <dledford@redhat.com>,
Jason Gunthorpe <jgg@nvidia.com>,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-next v2] IB/core: Only update PKEY and GID caches on respective events
Date: Thu, 6 May 2021 14:27:58 +0300 [thread overview]
Message-ID: <YJPSvu5c8K5ACSI+@unreal> (raw)
In-Reply-To: <1620289904-27687-1-git-send-email-haakon.bugge@oracle.com>
On Thu, May 06, 2021 at 10:31:44AM +0200, Håkon Bugge wrote:
> Both the PKEY and GID tables in an HCA can hold in the order of
> hundreds entries. Reading them are expensive. Partly because the API
> for retrieving them only returns a single entry at a time. Further, on
> certain implementations, e.g., CX-3, the VFs are paravirtualized in
> this respect and have to rely on the PF driver to perform the
> read. This again demands VF to PF communication.
>
> IB Core's cache is refreshed on all events. Hence, filter the refresh
> of the PKEY and GID caches based on the event received being
> IB_EVENT_PKEY_CHANGE and IB_EVENT_GID_CHANGE respectively.
>
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Signed-off-by: Håkon Bugge <haakon.bugge@oracle.com>
>
> ---
>
> v1 -> v2:
> * Changed signature of ib_cache_update() as per Leon's suggestion
> * Added Fixes tag as per Zhu Yanjun' suggestion
> ---
> drivers/infiniband/core/cache.c | 23 +++++++++++++++--------
> 1 file changed, 15 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/infiniband/core/cache.c b/drivers/infiniband/core/cache.c
> index 5c9fac7..1493a60 100644
> --- a/drivers/infiniband/core/cache.c
> +++ b/drivers/infiniband/core/cache.c
> @@ -1472,10 +1472,12 @@ static int config_non_roce_gid_cache(struct ib_device *device,
> }
>
> static int
> -ib_cache_update(struct ib_device *device, u8 port, bool enforce_security)
> +ib_cache_update(struct ib_device *device, u8 port, bool update_gids,
> + bool update_pkeys, bool enforce_security)
> {
> struct ib_port_attr *tprops = NULL;
> - struct ib_pkey_cache *pkey_cache = NULL, *old_pkey_cache;
> + struct ib_pkey_cache *pkey_cache = NULL;
> + struct ib_pkey_cache *old_pkey_cache = NULL;
> int i;
> int ret;
>
> @@ -1492,14 +1494,16 @@ static int config_non_roce_gid_cache(struct ib_device *device,
> goto err;
> }
>
> - if (!rdma_protocol_roce(device, port)) {
> + if (!rdma_protocol_roce(device, port) && update_gids) {
Can you please elaborate why it is safe to do for IB_EVENT_GID_CHANGE only?
What about IB_EVENT_CLIENT_REREGISTER?
Thanks
next prev parent reply other threads:[~2021-05-06 11:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 8:31 [PATCH for-next v2] IB/core: Only update PKEY and GID caches on respective events Håkon Bugge
2021-05-06 11:27 ` Leon Romanovsky [this message]
2021-05-06 12:22 ` Haakon Bugge
2021-05-09 7:47 ` Leon Romanovsky
2021-05-24 10:26 ` Haakon Bugge
2021-05-25 15:12 ` Jason Gunthorpe
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=YJPSvu5c8K5ACSI+@unreal \
--to=leon@kernel.org \
--cc=dledford@redhat.com \
--cc=haakon.bugge@oracle.com \
--cc=jgg@nvidia.com \
--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