From: <kirankumark@marvell.com>
To: Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>,
Harman Kalra <hkalra@marvell.com>
Cc: <dev@dpdk.org>
Subject: [PATCH v3 2/2] drivers: add support for IB_BTH header for RSS in cnxk device
Date: Wed, 30 Apr 2025 14:40:51 +0530 [thread overview]
Message-ID: <20250430091051.789240-2-kirankumark@marvell.com> (raw)
In-Reply-To: <20250430091051.789240-1-kirankumark@marvell.com>
From: Kiran Kumar K <kirankumark@marvell.com>
Adding support for IB_BTH header for RSS in cnxk device.
Signed-off-by: Kiran Kumar K <kirankumark@marvell.com>
---
drivers/common/cnxk/roc_mbox.h | 1 +
drivers/net/cnxk/cnxk_ethdev.c | 3 +++
drivers/net/cnxk/cnxk_ethdev.h | 2 +-
3 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/common/cnxk/roc_mbox.h b/drivers/common/cnxk/roc_mbox.h
index a82d120d1d..030556c8dc 100644
--- a/drivers/common/cnxk/roc_mbox.h
+++ b/drivers/common/cnxk/roc_mbox.h
@@ -1777,6 +1777,7 @@ struct nix_rss_flowkey_cfg {
#define FLOW_KEY_TYPE_CH_LEN_90B BIT(18)
#define FLOW_KEY_TYPE_CUSTOM0 BIT(19)
#define FLOW_KEY_TYPE_VLAN BIT(20)
+#define FLOW_KEY_TYPE_ROCEV2 BIT(24)
#define FLOW_KEY_TYPE_L4_DST BIT(28)
#define FLOW_KEY_TYPE_L4_SRC BIT(29)
#define FLOW_KEY_TYPE_L3_DST BIT(30)
diff --git a/drivers/net/cnxk/cnxk_ethdev.c b/drivers/net/cnxk/cnxk_ethdev.c
index 026c61f2c7..9500e92172 100644
--- a/drivers/net/cnxk/cnxk_ethdev.c
+++ b/drivers/net/cnxk/cnxk_ethdev.c
@@ -939,6 +939,9 @@ cnxk_rss_ethdev_to_nix(struct cnxk_eth_dev *dev, uint64_t ethdev_rss,
if (ethdev_rss & RTE_ETH_RSS_GTPU)
flowkey_cfg |= FLOW_KEY_TYPE_GTPU;
+ if (ethdev_rss & RTE_ETH_RSS_IB_BTH)
+ flowkey_cfg |= FLOW_KEY_TYPE_ROCEV2;
+
return flowkey_cfg;
}
diff --git a/drivers/net/cnxk/cnxk_ethdev.h b/drivers/net/cnxk/cnxk_ethdev.h
index daf80be51b..4f9802c5fa 100644
--- a/drivers/net/cnxk/cnxk_ethdev.h
+++ b/drivers/net/cnxk/cnxk_ethdev.h
@@ -59,7 +59,7 @@
(RTE_ETH_RSS_PORT | RTE_ETH_RSS_IP | RTE_ETH_RSS_UDP | \
RTE_ETH_RSS_TCP | RTE_ETH_RSS_SCTP | RTE_ETH_RSS_TUNNEL | \
RTE_ETH_RSS_L2_PAYLOAD | CNXK_NIX_RSS_L3_L4_SRC_DST | \
- RTE_ETH_RSS_LEVEL_MASK | RTE_ETH_RSS_C_VLAN)
+ RTE_ETH_RSS_LEVEL_MASK | RTE_ETH_RSS_C_VLAN | RTE_ETH_RSS_IB_BTH)
#define CNXK_NIX_TX_OFFLOAD_CAPA \
(RTE_ETH_TX_OFFLOAD_MBUF_FAST_FREE | RTE_ETH_TX_OFFLOAD_MT_LOCKFREE | \
--
2.48.1
next prev parent reply other threads:[~2025-04-30 9:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 5:14 [PATCH] ethdev: support RSS based on RoCEv2 header kirankumark
2025-04-23 0:06 ` Thomas Monjalon
2025-04-23 17:30 ` Stephen Hemminger
2025-04-29 9:52 ` [PATCH v2 1/2] " kirankumark
2025-04-29 9:52 ` [PATCH v2 2/2] drivers: add support for IB_BTH header for RSS in cnxk device kirankumark
2025-04-29 15:06 ` [PATCH v2 1/2] ethdev: support RSS based on RoCEv2 header Stephen Hemminger
2025-04-30 9:10 ` [PATCH v3 " kirankumark
2025-04-30 9:10 ` kirankumark [this message]
2025-04-30 10:20 ` [PATCH v4 " kirankumark
2025-04-30 10:20 ` [PATCH v4 2/2] drivers: add support for IB_BTH header for RSS in cnxk device kirankumark
2025-04-30 14:12 ` Stephen Hemminger
2025-04-30 14:48 ` [PATCH v4 1/2] ethdev: support RSS based on RoCEv2 header Stephen Hemminger
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=20250430091051.789240-2-kirankumark@marvell.com \
--to=kirankumark@marvell.com \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.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).