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>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v4 1/2] ethtool: treat RXH_GTP_TEID as intrinsically symmetric
Date: Sat, 14 Mar 2026 08:13:28 -0700 [thread overview]
Message-ID: <20260314081328.2635a33d@kernel.org> (raw)
In-Reply-To: <IA3PR11MB8986CA12EE22E9C07BCE7E83E545A@IA3PR11MB8986.namprd11.prod.outlook.com>
On Fri, 13 Mar 2026 11:28:29 +0000 Loktionov, Aleksandr wrote:
> > -----Original Message-----
> > From: Jakub Kicinski <kuba@kernel.org>
> > Sent: Thursday, March 12, 2026 3:42 PM
> > To: Loktionov, Aleksandr <aleksandr.loktionov@intel.com>
> > Cc: intel-wired-lan@lists.osuosl.org; netdev@vger.kernel.org; Nguyen,
> > Anthony L <anthony.l.nguyen@intel.com>
> > Subject: Re: [PATCH iwl-next v4 1/2] ethtool: treat RXH_GTP_TEID as
> > intrinsically symmetric
> >
> > On Thu, 12 Mar 2026 10:31:00 +0100 Aleksandr Loktionov wrote:
> > > + /* Strip TEID before checking - it carries no src/dst asymmetry
> > */
> > > + rxfh &= ~(u64)RXH_GTP_TEID;
> >
> > No need for the u64 cast.
>
> But without (u64) it will work only while it defined as implicit int
> #define RXH_GTP_TEID (1 << 8)
>
> When it will be defined as BIT(8) or unsigned int it will break.
> What you'd recommend preventing such issues in the future?
We will convert the 1 to 1ULL once we actually allocate the previous 31
bits? The type is only u64 because it may come from a UINT but the upper
bits must be zeros right now.
WARNING: multiple messages have this Message-ID (diff)
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>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>
Subject: Re: [PATCH iwl-next v4 1/2] ethtool: treat RXH_GTP_TEID as intrinsically symmetric
Date: Sat, 14 Mar 2026 08:13:28 -0700 [thread overview]
Message-ID: <20260314081328.2635a33d@kernel.org> (raw)
In-Reply-To: <IA3PR11MB8986CA12EE22E9C07BCE7E83E545A@IA3PR11MB8986.namprd11.prod.outlook.com>
On Fri, 13 Mar 2026 11:28:29 +0000 Loktionov, Aleksandr wrote:
> > -----Original Message-----
> > From: Jakub Kicinski <kuba@kernel.org>
> > Sent: Thursday, March 12, 2026 3:42 PM
> > To: Loktionov, Aleksandr <aleksandr.loktionov@intel.com>
> > Cc: intel-wired-lan@lists.osuosl.org; netdev@vger.kernel.org; Nguyen,
> > Anthony L <anthony.l.nguyen@intel.com>
> > Subject: Re: [PATCH iwl-next v4 1/2] ethtool: treat RXH_GTP_TEID as
> > intrinsically symmetric
> >
> > On Thu, 12 Mar 2026 10:31:00 +0100 Aleksandr Loktionov wrote:
> > > + /* Strip TEID before checking - it carries no src/dst asymmetry
> > */
> > > + rxfh &= ~(u64)RXH_GTP_TEID;
> >
> > No need for the u64 cast.
>
> But without (u64) it will work only while it defined as implicit int
> #define RXH_GTP_TEID (1 << 8)
>
> When it will be defined as BIT(8) or unsigned int it will break.
> What you'd recommend preventing such issues in the future?
We will convert the 1 to 1ULL once we actually allocate the previous 31
bits? The type is only u64 because it may come from a UINT but the upper
bits must be zeros right now.
next prev parent reply other threads:[~2026-03-14 15:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 9:30 [Intel-wired-lan] [PATCH iwl-next v4 0/2] ice: implement symmetric RSS hash configuration Aleksandr Loktionov
2026-03-12 9:30 ` Aleksandr Loktionov
2026-03-12 9:31 ` [Intel-wired-lan] [PATCH iwl-next v4 1/2] ethtool: treat RXH_GTP_TEID as intrinsically symmetric Aleksandr Loktionov
2026-03-12 9:31 ` Aleksandr Loktionov
2026-03-12 14:42 ` [Intel-wired-lan] " Jakub Kicinski
2026-03-12 14:42 ` Jakub Kicinski
2026-03-13 11:28 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-03-13 11:28 ` Loktionov, Aleksandr
2026-03-14 15:13 ` Jakub Kicinski [this message]
2026-03-14 15:13 ` Jakub Kicinski
2026-03-12 9:31 ` [Intel-wired-lan] [PATCH iwl-next v4 2/2] ice: implement symmetric RSS hash configuration Aleksandr Loktionov
2026-03-12 9:31 ` Aleksandr Loktionov
-- strict thread matches above, loose matches on Subject: below --
2026-02-26 14:40 [Intel-wired-lan] [PATCH iwl-next v4 0/2] " Aleksandr Loktionov
2026-02-26 14:40 ` [Intel-wired-lan] [PATCH iwl-next v4 1/2] ethtool: treat RXH_GTP_TEID as intrinsically symmetric 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=20260314081328.2635a33d@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 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.