[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231127085552.396f9375@kernel.org>
Date: Mon, 27 Nov 2023 08:55:52 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Ahmed Zaki <ahmed.zaki@...el.com>, Edward Cree <ecree.xilinx@...il.com>
Cc: <netdev@...r.kernel.org>, <intel-wired-lan@...ts.osuosl.org>,
<corbet@....net>, <jesse.brandeburg@...el.com>,
<anthony.l.nguyen@...el.com>, <davem@...emloft.net>, <edumazet@...gle.com>,
<pabeni@...hat.com>, <vladimir.oltean@....com>, <andrew@...n.ch>,
<horms@...nel.org>, <mkubecek@...e.cz>, <willemdebruijn.kernel@...il.com>,
<gal@...dia.com>, <alexander.duyck@...il.com>, <linux-doc@...r.kernel.org>,
Igor Bagnucki <igor.bagnucki@...el.com>, Jacob Keller
<jacob.e.keller@...el.com>
Subject: Re: [PATCH net-next v6 1/7] net: ethtool: pass ethtool_rxfh to
get/set_rxfh ethtool ops
On Mon, 27 Nov 2023 07:14:51 -0700 Ahmed Zaki wrote:
> > - First simplify the code by always providing a pointer to all params
> > (indir, key and func); the fact that some of them may be NULL seems
> > like a weird historic thing or a premature optimization.
> > It will simplify the drivers if all pointers are always present.
> > You don't have to remove the if () checks in the existing drivers.
> >
> > - Then make the functions take a dev pointer, and a pointer to a
> > single struct wrapping all arguments. The set_* should also take
> > an extack.
>
> Can we skip the "extack" part for this series? There is no
> "ETHTOOL_MSG_RSS_SET" netlink message, which is needed for user-space to
> get the ACK and adding all the netlink stuff seems a bit out of scope.
Fair point, yes, that's fine.
BTW, Ed, this series will conflict with your RSS context rework.
Not sure if it is on your radar.
Powered by blists - more mailing lists