From: Jakub Kicinski <kuba@kernel.org>
To: "Loktionov, Aleksandr" <aleksandr.loktionov@intel.com>
Cc: "intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH iwl-next v5 2/2] ice: implement symmetric RSS hash configuration
Date: Mon, 29 Jun 2026 15:53:43 -0700 [thread overview]
Message-ID: <20260629155343.7fed8291@kernel.org> (raw)
In-Reply-To: <IA3PR11MB8986053B156CBA043045A525E5E82@IA3PR11MB8986.namprd11.prod.outlook.com>
On Mon, 29 Jun 2026 14:10:08 +0000 Loktionov, Aleksandr wrote:
> I understood on TEID; I will drop the ethtool core patch.
>
> One question before respinning the ice feature patch: ice GTP RSS profiles
> include TEID in the hardware hash fields. Since TEID is not generally
> symmetric across UL/DL, should the driver:
>
> 1. report RXH_GTP_TEID honestly and let the core reject symmetric-xor
> when GTP flow types are part of the preflight check;
>
> 2. hide RXH_GTP_TEID while symmetric-xor is enabled, even though that
> misrepresents the hardware hash input;
>
> 3. reject symmetric-xor for configurations where GTP profiles include
> TEID; or
>
> 4. change/program the ice GTP profile, if possible, to exclude TEID
> under symmetric-xor?
>
> My preference is (1) or (3), but I do not want to encode the wrong uAPI
> semantics.
Do you have access to any GTP experts?
If your customers want the TEID in the symmetric hash then they
probably know better what makes sense than me after reading about it
for 1 minute.
We may just need a better commit message on the first patch "TEID is
intrinsically symmetric" is not true.
Or maybe the driver / profiles are not doing the right thing.
Please dig deeper.
next prev parent reply other threads:[~2026-06-29 22:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 5:47 [PATCH iwl-next v5 0/2] ice: implement symmetric RSS hash configuration Aleksandr Loktionov
2026-06-26 5:47 ` [PATCH iwl-next v5 1/2] ethtool: treat RXH_GTP_TEID as intrinsically symmetric Aleksandr Loktionov
2026-06-26 22:29 ` Jakub Kicinski
2026-06-26 5:47 ` [PATCH iwl-next v5 2/2] ice: implement symmetric RSS hash configuration Aleksandr Loktionov
2026-06-26 22:26 ` Jakub Kicinski
2026-06-29 14:10 ` Loktionov, Aleksandr
2026-06-29 22:53 ` Jakub Kicinski [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-16 7:20 [PATCH iwl-next v5 0/2] " Aleksandr Loktionov
2026-03-16 7:20 ` [PATCH iwl-next v5 2/2] " Aleksandr Loktionov
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=20260629155343.7fed8291@kernel.org \
--to=kuba@kernel.org \
--cc=aleksandr.loktionov@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox