From: Stephen Hemminger <stephen@networkplumber.org>
To: <kirankumark@marvell.com>
Cc: Aman Singh <aman.deep.singh@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Ferruh Yigit <ferruh.yigit@amd.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>, <dev@dpdk.org>
Subject: Re: [PATCH v6 1/2] ethdev: support RSS based on RoCEv2 header
Date: Tue, 20 May 2025 08:17:09 -0700 [thread overview]
Message-ID: <20250520081709.105c8b84@hermes.local> (raw)
In-Reply-To: <20250505055717.3697335-1-kirankumark@marvell.com>
On Mon, 5 May 2025 11:27:15 +0530
<kirankumark@marvell.com> wrote:
> @@ -149,6 +151,7 @@ const struct rss_type_info rss_type_table[] = {
> { "l3-dst-only", RTE_ETH_RSS_L3_DST_ONLY },
> { "l3-src-only", RTE_ETH_RSS_L3_SRC_ONLY },
> { "ipv6-flow-label", RTE_ETH_RSS_IPV6_FLOW_LABEL },
> + { "ib_bth", RTE_ETH_RSS_IB_BTH },
Please follow convention of other options. Use minus instead of underscore.
Consistency matters.
> diff --git a/doc/guides/rel_notes/release_25_07.rst b/doc/guides/rel_notes/release_25_07.rst
> index 093b85d206..d1293893be 100644
> --- a/doc/guides/rel_notes/release_25_07.rst
> +++ b/doc/guides/rel_notes/release_25_07.rst
> @@ -55,6 +55,10 @@ New Features
> Also, make sure to start the actual text at the margin.
> =======================================================
>
> +* **Added new RSS offload types for IB_BTH in RSS flow.**
> +
> + Added ``RTE_ETH_RSS_IB_BTH`` macro so that the IB BTH header can be used as input set for RSS.
> +
Please add reference to the relevant standard and expand the acronym
at least one place in the documentation.
> diff --git a/lib/ethdev/rte_ethdev.h b/lib/ethdev/rte_ethdev.h
> index ea7f8c4a1a..edcd6b75b5 100644
> --- a/lib/ethdev/rte_ethdev.h
> +++ b/lib/ethdev/rte_ethdev.h
> @@ -602,6 +602,7 @@ struct rte_eth_rss_conf {
>
> #define RTE_ETH_RSS_L2TPV2 RTE_BIT64(36)
> #define RTE_ETH_RSS_IPV6_FLOW_LABEL RTE_BIT64(37)
> +#define RTE_ETH_RSS_IB_BTH RTE_BIT64(38)
>
Why is the acronym IB_BTH rather than ROCEV2?
Wouldn't it be clearer if it followed convention?
prev parent reply other threads:[~2025-05-20 15:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 5:14 [PATCH] " 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 ` [PATCH v3 2/2] drivers: add support for IB_BTH header for RSS in cnxk device kirankumark
2025-04-30 10:20 ` [PATCH v4 1/2] ethdev: support RSS based on RoCEv2 header 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
2025-05-05 5:33 ` [PATCH v5 " kirankumark
2025-05-05 5:33 ` [PATCH v5 2/2] drivers: add support for IB_BTH header for RSS in cnxk device kirankumark
2025-05-05 5:57 ` [PATCH v6 1/2] ethdev: support RSS based on RoCEv2 header kirankumark
2025-05-05 5:57 ` [PATCH v6 2/2] drivers: add support for IB_BTH header for RSS in cnxk device kirankumark
2025-05-20 15:17 ` Stephen Hemminger [this message]
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=20250520081709.105c8b84@hermes.local \
--to=stephen@networkplumber.org \
--cc=aman.deep.singh@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=kirankumark@marvell.com \
--cc=thomas@monjalon.net \
/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).