From: Leon Romanovsky <leon@kernel.org>
To: Doug Ledford <dledford@redhat.com>, Jason Gunthorpe <jgg@mellanox.com>
Cc: Leon Romanovsky <leonro@mellanox.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>,
Daniel Jurgens <danielj@mellanox.com>,
Parav Pandit <parav@mellanox.com>
Subject: [PATCH rdma-next v1 0/2] Let IB core distribute cache update events
Date: Tue, 29 Oct 2019 13:53:25 +0200 [thread overview]
Message-ID: <20191029115327.16589-1-leon@kernel.org> (raw)
From: Leon Romanovsky <leonro@mellanox.com>
Changelog:
v0->v1: https://lore.kernel.org/linux-rdma/20191020065427.8772-1-leon@kernel.org
- Instead of conditionally notifying event in wq, always use WQ
This will allow to simplify the IB core and ULPs to get rid of
additional work.
- Updated kdoc comment to reflect the notifier execution context.
--------------------------------------------------------------------------------------
From Parav,
Currently when low level driver notifies Pkey, GID, port change
events, they are notified to the registered handlers in the order
they are registered.
IB core and other ULPs such as IPoIB are interested in GID, LID,
Pkey change events. Since all GID query done by ULPs is serviced
by IB core, IB core is yet to update the GID cache when IPoIB
queries the GID, resulting into not updating IPoIB address.
Detailed flow is shown in the patch-1.
Hence, all events which require cache update are handled first by
the IB core. Once cache update work is completed, IB core distributes
the event to subscriber clients.
This is tested with opensm's /etc/rdma/opensm.conf subnet_prefix
configuration update where before the update
$ ip link show dev ib0
ib0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 2044 qdisc pfifo_fast
state UP mode DEFAULT group default qlen 256
link/infiniband
80:00:01:07:fe:80:00:00:00:00:00:00:24:8a:07:03:00:b3:d1:12 brd
00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff
And after the subnet prefix update:
ib0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 2044 qdisc pfifo_fast
state UP mode DEFAULT group default qlen 256
link/infiniband
80:00:01:07:fe:80:00:00:00:00:00:02:24:8a:07:03:00:b3:d1:12 brd
00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff
Parav Pandit (2):
IB/core: Let IB core distribute cache update events
IB/core: Cut down single member ib_cache structure
drivers/infiniband/core/cache.c | 114 +++++++++++++---------------
drivers/infiniband/core/core_priv.h | 2 +
drivers/infiniband/core/device.c | 27 ++++---
include/rdma/ib_verbs.h | 8 +-
4 files changed, 74 insertions(+), 77 deletions(-)
--
2.20.1
next reply other threads:[~2019-10-29 11:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 11:53 Leon Romanovsky [this message]
2019-10-29 11:53 ` [PATCH rdma-next v1 1/2] IB/core: Let IB core distribute cache update events Leon Romanovsky
2019-10-29 13:31 ` Parav Pandit
2019-10-29 15:24 ` Jason Gunthorpe
2019-10-29 15:32 ` Parav Pandit
2019-10-29 15:33 ` Jason Gunthorpe
2019-10-29 15:47 ` Parav Pandit
2019-10-29 15:54 ` Jason Gunthorpe
2019-10-29 18:11 ` Parav Pandit
2019-10-29 18:26 ` Jason Gunthorpe
2019-10-29 19:28 ` Parav Pandit
2019-10-29 11:53 ` [PATCH rdma-next v1 2/2] IB/core: Cut down single member ib_cache structure Leon Romanovsky
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=20191029115327.16589-1-leon@kernel.org \
--to=leon@kernel.org \
--cc=danielj@mellanox.com \
--cc=dledford@redhat.com \
--cc=jgg@mellanox.com \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=parav@mellanox.com \
/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