[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20231207084506.727fc175@kernel.org>
Date: Thu, 7 Dec 2023 08:45:06 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Edward Cree <ecree.xilinx@...il.com>
Cc: edward.cree@....com, linux-net-drivers@....com, davem@...emloft.net,
edumazet@...gle.com, pabeni@...hat.com, netdev@...r.kernel.org,
habetsm.xilinx@...il.com, sudheer.mogilappagari@...el.com,
jdamato@...tly.com, andrew@...n.ch, mw@...ihalf.com, linux@...linux.org.uk,
sgoutham@...vell.com, gakula@...vell.com, sbhatta@...vell.com,
hkelam@...vell.com, saeedm@...dia.com, leon@...nel.org
Subject: Re: [PATCH v4 net-next 6/7] net: ethtool: add a mutex protecting
RSS contexts
On Thu, 7 Dec 2023 14:15:30 +0000 Edward Cree wrote:
> tl;dr: none of this is impossible, but it'd be a lot of work just to
> get rid of one mutex, and would paint us into a bit of a corner.
> So I propose to stick with the locking scheme for now; I'll post v5
> with the other review comments addressed; and if at some point in
> the future core tracking of ntuple filters gets added, we can
> revisit then whether moving to a replay scheme is viable. Okay?
Sounds good, thanks for investigating.
Powered by blists - more mailing lists