From: Simon Horman <horms@kernel.org>
To: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, anthony.l.nguyen@intel.com,
netdev@vger.kernel.org, mschmidt@redhat.com,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Dan Nowlin <dan.nowlin@intel.com>,
Qi Zhang <qi.z.zhang@intel.com>,
Jedrzej Jagielski <jedrzej.jagielski@intel.com>
Subject: Re: [PATCH iwl-next v4 4/5] ice: Extend PTYPE bitmap coverage for GTP encapsulated flows
Date: Fri, 12 Sep 2025 10:03:40 +0100 [thread overview]
Message-ID: <20250912090340.GX30363@horms.kernel.org> (raw)
In-Reply-To: <20250829101809.1022945-5-aleksandr.loktionov@intel.com>
On Fri, Aug 29, 2025 at 10:18:07AM +0000, Aleksandr Loktionov wrote:
> From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
>
> Consolidate updates to the Protocol Type (PTYPE) bitmap definitions
> across multiple flow types in the Intel ICE driver to support GTP
> (GPRS Tunneling Protocol) encapsulated traffic.
>
> Enable improved Receive Side Scaling (RSS) configuration for both user
> and control plane GTP flows.
>
> Cover a wide range of protocol and encapsulation scenarios, including:
> - MAC OFOS and IL
> - IPv4 and IPv6 (OFOS, IL, ALL, no-L4)
> - TCP, SCTP, ICMP
> - GRE OF
> - GTPC (control plane)
>
> Expand the PTYPE bitmap entries to improve classification and
> distribution of GTP traffic across multiple queues, enhancing
> performance and scalability in mobile network environments.
>
> Co-developed-by: Dan Nowlin <dan.nowlin@intel.com>
> Signed-off-by: Dan Nowlin <dan.nowlin@intel.com>
> Co-developed-by: Qi Zhang <qi.z.zhang@intel.com>
> Signed-off-by: Qi Zhang <qi.z.zhang@intel.com>
> Co-developed-by: Jie Wang <jie1x.wang@intel.com>
> Signed-off-by: Jie Wang <jie1x.wang@intel.com>
> Co-developed-by: Junfeng Guo <junfeng.guo@intel.com>
> Signed-off-by: Junfeng Guo <junfeng.guo@intel.com>
> Signed-off-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
> Signed-off-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
> Reviewed-by: Jedrzej Jagielski <jedrzej.jagielski@intel.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2025-09-12 9:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 10:18 [PATCH iwl-next v4 0/5] iavf and ice: GTP RSS support and flow enhancements Aleksandr Loktionov
2025-08-29 10:18 ` [PATCH iwl-next v4 1/5] ice: add flow parsing for GTP and new protocol field support Aleksandr Loktionov
2025-09-12 9:03 ` Simon Horman
2025-09-12 10:04 ` [Intel-wired-lan] " Paul Menzel
2025-09-15 12:32 ` Loktionov, Aleksandr
2025-08-29 10:18 ` [PATCH iwl-next v4 2/5] ice: add virtchnl and VF context support for GTP RSS Aleksandr Loktionov
2025-09-12 9:02 ` Simon Horman
2025-09-13 4:41 ` [Intel-wired-lan] " Paul Menzel
2025-08-29 10:18 ` [PATCH iwl-next v4 3/5] ice: improve TCAM priority handling for RSS profiles Aleksandr Loktionov
2025-09-12 9:03 ` Simon Horman
2025-08-29 10:18 ` [PATCH iwl-next v4 4/5] ice: Extend PTYPE bitmap coverage for GTP encapsulated flows Aleksandr Loktionov
2025-09-12 9:03 ` Simon Horman [this message]
2025-08-29 10:18 ` [PATCH iwl-next v4 5/5] iavf: add RSS support for GTP protocol via ethtool Aleksandr Loktionov
2025-09-12 9:03 ` Simon Horman
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=20250912090340.GX30363@horms.kernel.org \
--to=horms@kernel.org \
--cc=aleksandr.loktionov@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=dan.nowlin@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jedrzej.jagielski@intel.com \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.com \
--cc=qi.z.zhang@intel.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).