From: Jason Gunthorpe <jgg@nvidia.com>
To: Anand Khoje <anand.a.khoje@oracle.com>
Cc: linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
dledford@redhat.com, haakon.bugge@oracle.com, leon@kernel.org
Subject: Re: [PATCH v8 for-next 0/3] IB/core: Obtaining subnet_prefix from cache in
Date: Fri, 16 Jul 2021 11:08:04 -0300 [thread overview]
Message-ID: <20210716140804.GA752808@nvidia.com> (raw)
In-Reply-To: <20210712122625.1147-1-anand.a.khoje@oracle.com>
On Mon, Jul 12, 2021 at 05:56:22PM +0530, Anand Khoje wrote:
> This v8 of patch series is used to read the port_attribute subnet_prefix
> from a valid cache entry instead of having to call
> device->ops.query_gid() for Infiniband link-layer devices in
> __ib_query_port().
>
> In the event of a cache update, the value for subnet_prefix gets read
> using device->ops.query_gid() in config_non_roce_gid_cache().
>
> It also re-orders the initialization of lock cache_lock of struct ib_device
> such that the lock is initialized before its first use in __ib_query_port()
> during device initialization.
>
> Anand Khoje (3):
> IB/core: Updating cache for subnet_prefix in
> config_non_roce_gid_cache()
> IB/core: Shifting initialization of device->cache_lock
> IB/core: Read subnet_prefix in ib_query_port via cache.
>
> drivers/infiniband/core/cache.c | 10 +++++-----
> drivers/infiniband/core/device.c | 10 ++++------
> 2 files changed, 9 insertions(+), 11 deletions(-)
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2021-07-16 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 12:26 [PATCH v8 for-next 0/3] IB/core: Obtaining subnet_prefix from cache in Anand Khoje
2021-07-12 12:26 ` [PATCH v8 for-next 1/3] IB/core: Updating cache for subnet_prefix in config_non_roce_gid_cache() Anand Khoje
2021-07-12 12:26 ` [PATCH v8 for-next 2/3] IB/core: Shifting initialization of device->cache_lock Anand Khoje
2021-07-12 12:26 ` [PATCH v8 for-next 3/3] IB/core: Read subnet_prefix in ib_query_port via cache Anand Khoje
2021-07-16 14:08 ` Jason Gunthorpe [this message]
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=20210716140804.GA752808@nvidia.com \
--to=jgg@nvidia.com \
--cc=anand.a.khoje@oracle.com \
--cc=dledford@redhat.com \
--cc=haakon.bugge@oracle.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.