[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YirqTaKPzmKLy6EB@unreal>
Date: Fri, 11 Mar 2022 08:21:01 +0200
From: Leon Romanovsky <leonro@...dia.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: Tony Nguyen <anthony.l.nguyen@...el.com>, <davem@...emloft.net>,
"Sridhar Samudrala" <sridhar.samudrala@...el.com>,
<netdev@...r.kernel.org>, <sudheer.mogilappagari@...el.com>,
<amritha.nambiar@...el.com>, <jiri@...dia.com>,
Bharathi Sreenivas <bharathi.sreenivas@...el.com>
Subject: Re: [PATCH net-next 1/2] devlink: Allow parameter
registration/unregistration during runtime
On Thu, Mar 10, 2022 at 08:33:48PM -0800, Jakub Kicinski wrote:
> On Thu, 10 Mar 2022 15:12:34 -0800 Tony Nguyen wrote:
> > From: Sridhar Samudrala <sridhar.samudrala@...el.com>
> >
> > commit 7a690ad499e7 ("devlink: Clean not-executed param notifications")
> > added ASSERTs and removed notifications when devlink parameters are
> > registered by the drivers after the associated devlink instance is
> > already registered.
> > The next patch in this series adds a feature in 'ice' driver that is
> > only enabled when ADQ queue groups are created and introduces a
> > devlink parameter to configure this feature per queue group.
> >
> > To allow dynamic parameter registration/unregistration during runtime,
> > revert the changes added by the above commit.
>
> I'm pretty sure what you're doing is broken. You should probably wait
> until my patches to allow explicit devlink locking are merged and build
> on top of that.
Yes, it is broken, but I don't see how your devlink locking series will
help here. IMHO, devlink_params_register() should not be dynamic [1].
Thanks
[1] https://lore.kernel.org/all/YirRQWT7dtTV4fwG@unreal
Powered by blists - more mailing lists