From: Edward Cree <ecree.xilinx@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>, davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
andrew+netdev@lunn.ch, horms@kernel.org, andrew@lunn.ch,
przemyslaw.kitszel@intel.com, anthony.l.nguyen@intel.com,
sgoutham@marvell.com, gakula@marvell.com, sbhatta@marvell.com,
bbhushan2@marvell.com, tariqt@nvidia.com, mbloch@nvidia.com,
leon@kernel.org, gal@nvidia.com
Subject: Re: [PATCH net-next v2 4/5] net: ethtool: remove the compat code for _rxfh_context ops
Date: Wed, 2 Jul 2025 19:54:36 +0100 [thread overview]
Message-ID: <11d9b133-0e98-4fb9-9290-40d8cbb08fa6@gmail.com> (raw)
In-Reply-To: <20250702030606.1776293-5-kuba@kernel.org>
On 02/07/2025 04:06, Jakub Kicinski wrote:
> All drivers are now converted to dedicated _rxfh_context ops.
> Remove the use of >set_rxfh() to manage additional contexts.
>
> Reviewed-by: Gal Pressman <gal@nvidia.com>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
...
> diff --git a/net/core/dev.c b/net/core/dev.c
> index 7ee808eb068e..ee32d87eb411 100644
> --- a/net/core/dev.c
> +++ b/net/core/dev.c
...
> @@ -1670,7 +1668,7 @@ static noinline_for_stack int ethtool_set_rxfh(struct net_device *dev,
> rxfh_dev.rss_context = rxfh.rss_context;
> rxfh_dev.input_xfrm = rxfh.input_xfrm;
>
> - if (rxfh.rss_context && ops->create_rxfh_context) {
> + if (rxfh.rss_context) {
> if (create) {
> ret = ops->create_rxfh_context(dev, ctx, &rxfh_dev,
> extack);
A few lines after this we have
if (ret) {
if (create) {
/* failed to create, free our new tracking entry */
if (ops->create_rxfh_context)
xa_erase(&dev->ethtool->rss_ctx, rxfh.rss_context);
kfree(ctx);
}
goto out;
}
AFAICT that 'if (ops->create_rxfh_context)' guard can also go, because it's
only false in the compat case.
> @@ -1712,37 +1710,6 @@ static noinline_for_stack int ethtool_set_rxfh(struct net_device *dev,
> else if (rxfh.indir_size != ETH_RXFH_INDIR_NO_CHANGE)
> dev->priv_flags |= IFF_RXFH_CONFIGURED;
> }
> - /* Update rss_ctx tracking */
This comment applies to not just the code being removed, but also the part
below that (if(delete), else if (ctx)) that's retained, please keep it.
Other than that this looks good. (Patches 1-3 look plausible but I don't
feel competent to review those drivers to the level of giving tags.)
next prev parent reply other threads:[~2025-07-02 18:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 3:06 [PATCH net-next v2 0/5] net: migrate remaining drivers to dedicated _rxfh_context ops Jakub Kicinski
2025-07-02 3:06 ` [PATCH net-next v2 1/5] eth: otx2: migrate to the *_rxfh_context ops Jakub Kicinski
2025-07-04 7:14 ` [EXTERNAL] " Geethasowjanya Akula
2025-07-02 3:06 ` [PATCH net-next v2 2/5] eth: ice: drop the dead code related to rss_contexts Jakub Kicinski
2025-07-02 3:06 ` [PATCH net-next v2 3/5] eth: mlx5: migrate to the *_rxfh_context ops Jakub Kicinski
2025-07-03 12:22 ` Gal Pressman
2025-07-07 18:19 ` Jakub Kicinski
2025-07-03 17:35 ` kernel test robot
2025-07-05 3:24 ` kernel test robot
2025-07-02 3:06 ` [PATCH net-next v2 4/5] net: ethtool: remove the compat code for _rxfh_context ops Jakub Kicinski
2025-07-02 18:54 ` Edward Cree [this message]
2025-07-02 3:06 ` [PATCH net-next v2 5/5] net: ethtool: reduce indent " Jakub Kicinski
2025-07-02 18:57 ` Edward Cree
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11d9b133-0e98-4fb9-9290-40d8cbb08fa6@gmail.com \
--to=ecree.xilinx@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=bbhushan2@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=tariqt@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).