From: Jason Gunthorpe <jgg@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Mark Bloch <mbloch@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
linux-rdma@vger.kernel.org, Mark Zhang <markzhang@nvidia.com>,
netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
Saeed Mahameed <saeedm@nvidia.com>
Subject: Re: [PATCH rdma-next 1/2] RDMA/mlx5: Get upper device only if device is lagged
Date: Mon, 21 Aug 2023 10:39:07 -0300 [thread overview]
Message-ID: <ZONo++BgYux82Wjo@nvidia.com> (raw)
In-Reply-To: <20230820095926.GE1562474@unreal>
On Sun, Aug 20, 2023 at 12:59:26PM +0300, Leon Romanovsky wrote:
> On Fri, Aug 18, 2023 at 01:42:30PM -0300, Jason Gunthorpe wrote:
> > On Fri, Aug 18, 2023 at 01:33:35PM -0300, Jason Gunthorpe wrote:
> > > On Wed, Aug 16, 2023 at 09:52:23AM +0300, Leon Romanovsky wrote:
> > > > From: Mark Bloch <mbloch@nvidia.com>
> > > >
> > > > If the RDMA device isn't in LAG mode there is no need
> > > > to try to get the upper device.
> > > >
> > > > Signed-off-by: Mark Bloch <mbloch@nvidia.com>
> > > > Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
> > > > ---
> > > > drivers/infiniband/hw/mlx5/main.c | 22 +++++++++++++++-------
> > > > 1 file changed, 15 insertions(+), 7 deletions(-)
> > > >
> > > > diff --git a/drivers/infiniband/hw/mlx5/main.c b/drivers/infiniband/hw/mlx5/main.c
> > > > index f0b394ed7452..215d7b0add8f 100644
> > > > --- a/drivers/infiniband/hw/mlx5/main.c
> > > > +++ b/drivers/infiniband/hw/mlx5/main.c
> > > > @@ -195,12 +195,18 @@ static int mlx5_netdev_event(struct notifier_block *this,
> > > > case NETDEV_CHANGE:
> > > > case NETDEV_UP:
> > > > case NETDEV_DOWN: {
> > > > - struct net_device *lag_ndev = mlx5_lag_get_roce_netdev(mdev);
> > > > struct net_device *upper = NULL;
> > > >
> > > > - if (lag_ndev) {
> > > > - upper = netdev_master_upper_dev_get(lag_ndev);
> > > > - dev_put(lag_ndev);
> > > > + if (ibdev->lag_active) {
> > >
> > > Needs locking to read lag_active
> >
> > Specifically the use of the bitfield looks messed up.. If lag_active
> > and some others were set only during probe it could be OK.
>
> All fields except ib_active are static and set during probe.
>
> >
> > But mixing other stuff that is being written concurrently is not OK to
> > do like this. (eg ib_active via a mlx5 notifier)
>
> What you are looking is the following change, did I get you right?
>
> diff --git a/drivers/infiniband/hw/mlx5/mlx5_ib.h b/drivers/infiniband/hw/mlx5/mlx5_ib.h
> index 9d0c56b59ed2..ee73113717b2 100644
> --- a/drivers/infiniband/hw/mlx5/mlx5_ib.h
> +++ b/drivers/infiniband/hw/mlx5/mlx5_ib.h
> @@ -1094,7 +1094,7 @@ struct mlx5_ib_dev {
> /* serialize update of capability mask
> */
> struct mutex cap_mask_mutex;
> - u8 ib_active:1;
> + bool ib_active;
> u8 is_rep:1;
> u8 lag_active:1;
> u8 wc_support:1;
That helps, but it still needs some kind of concurrency management for
ib_active
Jason
next prev parent reply other threads:[~2023-08-21 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 6:52 [PATCH rdma-next 0/2] mlx5 RDMA LAG fixes Leon Romanovsky
2023-08-16 6:52 ` [PATCH rdma-next 1/2] RDMA/mlx5: Get upper device only if device is lagged Leon Romanovsky
2023-08-18 16:33 ` Jason Gunthorpe
2023-08-18 16:42 ` Jason Gunthorpe
2023-08-20 9:59 ` Leon Romanovsky
2023-08-21 13:39 ` Jason Gunthorpe [this message]
2023-08-16 6:52 ` [PATCH rdma-next 2/2] RDMA/mlx5: Send correct port events 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=ZONo++BgYux82Wjo@nvidia.com \
--to=jgg@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=markzhang@nvidia.com \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.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 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.