All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Gal Pressman <gal@nvidia.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
	donald.hunter@gmail.com, shuah@kernel.org,
	kory.maincent@bootlin.com, maxime.chevallier@bootlin.com,
	sdf@fomichev.me, ecree.xilinx@gmail.com
Subject: Re: [PATCH net-next 09/11] ethtool: rss: support setting input-xfrm via Netlink
Date: Mon, 14 Jul 2025 09:27:59 -0700	[thread overview]
Message-ID: <20250714092759.3f8c77de@kernel.org> (raw)
In-Reply-To: <f894a965-3fb3-4068-9d1e-95ff62705544@nvidia.com>

On Sun, 13 Jul 2025 14:11:34 +0300 Gal Pressman wrote:
> > +	/* xfrm_input is NO_CHANGE AKA 0xff if per-context not supported */  
> 
> Can you please explain this comment? Shouldn't we fail in this case?
> Nit: xfrm_input -> input_xfrm.
> 
> > +	if (!request->rss_context || ops->rxfh_per_ctx_key)
> > +		xfrm_sym = !!rxfh.input_xfrm;

xfrm_sym is supposed to indicate whether input_xfrm is set to symmetric.
Normally !!input_xfrm will tell us, but if we're dealing with a request
for an RSS context and driver doesn't support per ctx key input_xfrm
will be 0xff so we'd false positive xfrm_sym and most likely fail the
SET request if the field config is not symmeric. I'll rewrite this.

BTW I have a check at netdev reg time to make sure all drivers which
support xfrm_sym and contexts also support per-context xfrm_sym, but 
it will conflict with your fix so I didn't include it, yet.

  reply	other threads:[~2025-07-14 16:28 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-11  1:52 [PATCH net-next 00/11] ethtool: rss: support RSS_SET via Netlink Jakub Kicinski
2025-07-11  1:52 ` [PATCH net-next 01/11] ethtool: rss: initial RSS_SET (indirection table handling) Jakub Kicinski
2025-07-13 11:08   ` Gal Pressman
2025-07-14 16:15     ` Jakub Kicinski
2025-07-11  1:52 ` [PATCH net-next 02/11] selftests: drv-net: rss_api: factor out checking min queue count Jakub Kicinski
2025-07-11  1:52 ` [PATCH net-next 03/11] tools: ynl: support packing binary arrays of scalars Jakub Kicinski
2025-07-11  1:52 ` [PATCH net-next 04/11] selftests: drv-net: rss_api: test setting indirection table via Netlink Jakub Kicinski
2025-07-14 22:19   ` Edward Cree
2025-07-14 22:28     ` Jakub Kicinski
2025-07-11  1:52 ` [PATCH net-next 05/11] ethtool: rss: support setting hfunc " Jakub Kicinski
2025-07-13 11:10   ` Gal Pressman
2025-07-14 16:21     ` Jakub Kicinski
2025-07-15  6:32       ` Gal Pressman
2025-07-11  1:52 ` [PATCH net-next 06/11] ethtool: rss: support setting hkey " Jakub Kicinski
2025-07-13 11:10   ` Gal Pressman
2025-07-11  1:52 ` [PATCH net-next 07/11] selftests: drv-net: rss_api: test setting hashing key " Jakub Kicinski
2025-07-11  1:53 ` [PATCH net-next 08/11] netlink: specs: define input-xfrm enum in the spec Jakub Kicinski
2025-07-13 13:20   ` Gal Pressman
2025-07-11  1:53 ` [PATCH net-next 09/11] ethtool: rss: support setting input-xfrm via Netlink Jakub Kicinski
2025-07-13 11:11   ` Gal Pressman
2025-07-14 16:27     ` Jakub Kicinski [this message]
2025-07-11  1:53 ` [PATCH net-next 10/11] ethtool: rss: support setting flow hashing fields Jakub Kicinski
2025-07-13 11:12   ` Gal Pressman
2025-07-14 16:29     ` Jakub Kicinski
2025-07-15 10:27       ` Gal Pressman
2025-07-15 14:50         ` Jakub Kicinski
2025-07-11  1:53 ` [PATCH net-next 11/11] selftests: drv-net: rss_api: test input-xfrm and hash fields Jakub Kicinski
2025-07-13 14:05   ` Gal Pressman
2025-07-14 16:31     ` Jakub Kicinski
2025-07-13 11:06 ` [PATCH net-next 00/11] ethtool: rss: support RSS_SET via Netlink Gal Pressman
2025-07-14 16:35   ` Jakub Kicinski
2025-07-15  6:33     ` Gal Pressman
2025-07-15 14:53       ` Jakub Kicinski

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=20250714092759.3f8c77de@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=ecree.xilinx@gmail.com \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=horms@kernel.org \
    --cc=kory.maincent@bootlin.com \
    --cc=maxime.chevallier@bootlin.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@fomichev.me \
    --cc=shuah@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.