[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230314212334.188ad6e0@kernel.org>
Date: Tue, 14 Mar 2023 21:23:34 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Edward Cree <ecree.xilinx@...il.com>
Cc: "Mogilappagari, Sudheer" <sudheer.mogilappagari@...el.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"mkubecek@...e.cz" <mkubecek@...e.cz>,
"Samudrala, Sridhar" <sridhar.samudrala@...el.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@...el.com>
Subject: Re: [PATCH net-next] ethtool: add netlink support for rss set
On Tue, 14 Mar 2023 13:34:51 +0000 Edward Cree wrote:
> > Add a pointer to struct
> > netdevice to hold an "ethtool_settings" struct. In the ethtool settings
> > struct add a list head. Put an object for each created RSS context on
> > that list.
> Would an IDR not be appropriate here, rather than a list?
Yup, I was too lazy how much memory IDR eats when unused, and list is
easier to explain, but let's just go for an xarray if you're doing it.
> AFAICT every driver that supports contexts either treats the context
> ID as an opaque handle or as an index into a fixed-size array, so as
> long as the driver reports its max context ID to the core somehow,
> the specific ID values chosen are arbitrary and the driver doesn't
> need to do the choosing, it can just take what comes out of the IDR.
Sounds great.
Powered by blists - more mailing lists