From: Sandeep Penigalapati <sandeep.penigalapati@intel.com>
To: dev@dpdk.org
Cc: bruce.richardson@intel.com,
Sandeep Penigalapati <sandeep.penigalapati@intel.com>
Subject: [PATCH] net/iavf: add fragment RSS types for symmetric Toeplitz
Date: Fri, 5 Dec 2025 12:55:37 -0500 [thread overview]
Message-ID: <20251205175537.137011-1-sandeep.penigalapati@intel.com> (raw)
The ICE PMD supports RTE_ETH_RSS_FRAG_IPV4 and RTE_ETH_RSS_FRAG_IPV6
with symmetric Toeplitz, but these were missing from IAVF PMD.
Added the fragment RSS types to enable fragment hashing support in VF,
matching the PF driver capability.
Signed-off-by: Sandeep Penigalapati <sandeep.penigalapati@intel.com>
---
.mailmap | 1 +
drivers/net/intel/iavf/iavf_hash.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/.mailmap b/.mailmap
index 2f089326ff..fa2e10afe8 100644
--- a/.mailmap
+++ b/.mailmap
@@ -1418,6 +1418,7 @@ Samik Gupta <samik.gupta@broadcom.com>
Samina Arshad <samina.arshad@intel.com>
Sampath Peechu <speechu@cisco.com>
Samuel Gauthier <samuel.gauthier@6wind.com>
+Sandeep Penigalapati <sandeep.penigalapati@intel.com>
Sandilya Bhagi <sbhagi@solarflare.com>
Sangjin Han <sangjin@eecs.berkeley.edu>
Sangtani Parag Satishbhai <parag-satishbhai.sangtani@broadcom.com>
diff --git a/drivers/net/intel/iavf/iavf_hash.c b/drivers/net/intel/iavf/iavf_hash.c
index 217f0500ab..72c77f75ac 100644
--- a/drivers/net/intel/iavf/iavf_hash.c
+++ b/drivers/net/intel/iavf/iavf_hash.c
@@ -1390,6 +1390,7 @@ iavf_any_invalid_rss_type(enum rte_eth_hash_function rss_func,
if (!(rss_type &
(RTE_ETH_RSS_IPV4 | RTE_ETH_RSS_IPV6 |
+ RTE_ETH_RSS_FRAG_IPV4 | RTE_ETH_RSS_FRAG_IPV6 |
RTE_ETH_RSS_NONFRAG_IPV4_UDP | RTE_ETH_RSS_NONFRAG_IPV6_UDP |
RTE_ETH_RSS_NONFRAG_IPV4_TCP | RTE_ETH_RSS_NONFRAG_IPV6_TCP |
RTE_ETH_RSS_NONFRAG_IPV4_SCTP | RTE_ETH_RSS_NONFRAG_IPV6_SCTP)))
--
2.43.5
reply other threads:[~2025-12-05 10:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20251205175537.137011-1-sandeep.penigalapati@intel.com \
--to=sandeep.penigalapati@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).