[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240906075627.523b66f9@kernel.org>
Date: Fri, 6 Sep 2024 07:56:27 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Paolo Abeni <pabeni@...hat.com>
Cc: netdev@...r.kernel.org, Jiri Pirko <jiri@...nulli.us>, Madhu Chittim
<madhu.chittim@...el.com>, Sridhar Samudrala <sridhar.samudrala@...el.com>,
Simon Horman <horms@...nel.org>, John Fastabend <john.fastabend@...il.com>,
Sunil Kovvuri Goutham <sgoutham@...vell.com>, Jamal Hadi Salim
<jhs@...atatu.com>, Donald Hunter <donald.hunter@...il.com>,
anthony.l.nguyen@...el.com, przemyslaw.kitszel@...el.com,
intel-wired-lan@...ts.osuosl.org, edumazet@...gle.com
Subject: Re: [PATCH v6 net-next 07/15] net-shapers: implement shaper cleanup
on queue deletion
On Fri, 6 Sep 2024 16:49:32 +0200 Paolo Abeni wrote:
> I forgot to mention there is another, easier, alternative: keep the max
> queue id check in the drivers. The driver will have to acquire and held
> in the shaper callbacks the relevant driver-specific lock - 'crit_lock',
> in the iavf case.
>
> Would you be ok with such 2nd option?
I'd strongly prefer if you implemented what was suggested.
> Side note: I think the iavf should have to acquire such lock in the
> callbacks no matter what or access/write to the rings info could be racy.
Powered by blists - more mailing lists