From: Thomas Monjalon <thomas@monjalon.net>
To: Kiran Kumar K <kirankumark@marvell.com>
Cc: Aman Singh <aman.deep.singh@intel.com>,
Ferruh Yigit <ferruh.yigit@amd.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
dev@dpdk.org, Dariusz Sosnowski <dsosnowski@nvidia.com>,
Ori Kam <orika@nvidia.com>
Subject: Re: [PATCH] ethdev: support RSS based on RoCEv2 header
Date: Wed, 23 Apr 2025 02:06:58 +0200 [thread overview]
Message-ID: <6153993.lOV4Wx5bFT@thomas> (raw)
In-Reply-To: <20250422051459.661395-1-kirankumark@marvell.com>
22/04/2025 07:14, kirankumark@marvell.com:
> From: Kiran Kumar K <kirankumark@marvell.com>
>
> On supporting hardware, RoCEv2 header can be used to
> perform RSS in the ingress path.
Do you mean IB BTH?
It would be good to adopt a unique name between RSS and flow matching:
RTE_FLOW_ITEM_TYPE_IB_BTH
next prev parent reply other threads:[~2025-04-23 0:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 5:14 kirankumark
2025-04-23 0:06 ` Thomas Monjalon [this message]
2025-04-23 17:30 ` 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=6153993.lOV4Wx5bFT@thomas \
--to=thomas@monjalon.net \
--cc=aman.deep.singh@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=ferruh.yigit@amd.com \
--cc=kirankumark@marvell.com \
--cc=orika@nvidia.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).