From: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
To: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
anthony.l.nguyen@intel.com, aleksandr.loktionov@intel.com
Subject: [PATCH iwl-next v3 0/5] iavf and ice: GTP RSS support and flow enhancements
Date: Fri, 20 Feb 2026 10:24:04 +0100 [thread overview]
Message-ID: <20260220092409.718632-1-aleksandr.loktionov@intel.com> (raw)
This patch series introduces support for Receive Side Scaling (RSS)
configuration of GTP (GPRS Tunneling Protocol) flows via the ethtool
interface on virtual function (VF) interfaces in the iavf driver.
The implementation enables fine-grained traffic distribution for
GTP-based mobile workloads, including GTPC and GTPU encapsulations, by
extending the advanced RSS infrastructure. This is particularly beneficial
for virtualized network functions (VNFs) and user plane functions (UPFs)
in 5G and LTE deployments.
Key features:
- Adds new RSS flow segment headers and hash field definitions for GTP
protocols.
- Enhances ethtool parsing logic to support GTP-specific flow types.
- Updates the virtchnl interface to propagate GTP RSS configuration to PF.
- Extends the ICE driver to support GTP RSS configuration for VFs.
changelog:
v2:
- reduce much repetition with ice_hash_{remove,moveout}() calls
(Przemek, leftover from internal review)
- now applies on Tony's tree
v1/RFC: https://lore.kernel.org/intel-wired-lan/20250811111213.2964512-1-aleksandr.loktionov@intel.com
Aleksandr Loktionov (4):
ice: add flow parsing for GTP and new protocol field support
ice: add virtchnl and VF context support for GTP RSS
ice: improve TCAM priority handling for RSS profiles
iavf: add RSS support for GTP protocol via ethtool
Przemek Kitszel (1):
ice: extend PTYPE bitmap coverage for GTP encapsulated flows
.../net/ethernet/intel/iavf/iavf_adv_rss.c | 119 +-
.../net/ethernet/intel/iavf/iavf_adv_rss.h | 31 +
.../net/ethernet/intel/iavf/iavf_ethtool.c | 89 ++
.../net/ethernet/intel/ice/ice_flex_pipe.c | 91 +-
.../net/ethernet/intel/ice/ice_flex_type.h | 1 +
drivers/net/ethernet/intel/ice/ice_flow.c | 251 ++-
drivers/net/ethernet/intel/ice/ice_flow.h | 94 +-
.../ethernet/intel/ice/ice_protocol_type.h | 20 +
drivers/net/ethernet/intel/ice/ice_vf_lib.h | 48 +
.../net/ethernet/intel/ice/ice_virtchnl_rss.c | 1404 ++++++++++++++++-
include/linux/avf/virtchnl.h | 50 +
11 files changed, 2070 insertions(+), 128 deletions(-)
--
2.47.1
next reply other threads:[~2026-02-20 9:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 9:24 Aleksandr Loktionov [this message]
2026-02-20 9:24 ` [PATCH iwl-next v3 1/5] ice: add flow parsing for GTP and new protocol field support Aleksandr Loktionov
2026-02-20 9:28 ` Loktionov, Aleksandr
2026-02-20 9:24 ` [PATCH iwl-next v3 2/5] ice: add virtchnl and VF context support for GTP RSS Aleksandr Loktionov
2026-02-20 9:27 ` Loktionov, Aleksandr
2026-02-20 9:24 ` [PATCH iwl-next v3 3/5] ice: improve TCAM priority handling for RSS profiles Aleksandr Loktionov
2026-02-20 9:28 ` Loktionov, Aleksandr
2026-02-20 9:24 ` [PATCH iwl-next v3 4/5] ice: Extend PTYPE bitmap coverage for GTP encapsulated flows Aleksandr Loktionov
2026-02-20 9:28 ` Loktionov, Aleksandr
2026-02-20 9:27 ` [PATCH iwl-next v3 0/5] iavf and ice: GTP RSS support and flow enhancements Loktionov, Aleksandr
-- strict thread matches above, loose matches on Subject: below --
2025-08-27 18:53 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=20260220092409.718632-1-aleksandr.loktionov@intel.com \
--to=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