[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <067db690-b92b-7005-fa9a-4559b7d6de8d@intel.com>
Date: Fri, 29 Sep 2023 11:27:55 -0700
From: Jacob Keller <jacob.e.keller@...el.com>
To: <edward.cree@....com>, <linux-net-drivers@....com>, <davem@...emloft.net>,
<kuba@...nel.org>, <edumazet@...gle.com>, <pabeni@...hat.com>
CC: Edward Cree <ecree.xilinx@...il.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 7/7] sfc: use new rxfh_context API
On 9/27/2023 11:13 AM, edward.cree@....com wrote:
> From: Edward Cree <ecree.xilinx@...il.com>
>
> The core is now responsible for allocating IDs and a memory region for
> us to store our state (struct efx_rss_context_priv), so we no longer
> need efx_alloc_rss_context_entry() and friends.
> Since the contexts are now maintained by the core, use the core's lock
> (net_dev->ethtool->rss_lock), rather than our own mutex (efx->rss_lock),
> to serialise access against changes; and remove the now-unused
> efx->rss_lock from struct efx_nic.
>
> Signed-off-by: Edward Cree <ecree.xilinx@...il.com>
Reviewed-by: Jacob Keller <jacob.e.keller@...el.com>
Powered by blists - more mailing lists