From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>, dev@dpdk.org
Cc: andrew.rybchenko@oktetlabs.ru
Subject: Re: [PATCH v3] ethdev: add support for RSS based on IPv6 flow label
Date: Fri, 9 Feb 2024 22:45:41 +0000 [thread overview]
Message-ID: <9dfc174f-47a0-41bf-a32d-4100dc8a0ba0@amd.com> (raw)
In-Reply-To: <20240209181615.84171-1-ajit.khaparde@broadcom.com>
On 2/9/2024 6:16 PM, Ajit Khaparde wrote:
> On supporting hardware, the 20-bit Flow Label field in the
> IPv6 header can be used to perform RSS in the ingress path.
>
> Flow label values can be chosen such that they can be
> used as part of the input to a hash function used in a load
> distribution scheme.
>
> Example to configure IPv6 flow label based RSS:
> flow create 0 ingress pattern eth / ipv6 / tcp / end actions rss types ipv6-flow-label end / end
>
> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
>
Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2024-02-09 22:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 5:43 [PATCH 0/3] Support IPv6 flow label based RSS Ajit Khaparde
2024-02-08 5:43 ` [PATCH 1/3] ethdev: add support for RSS based on IPv6 flow label Ajit Khaparde
2024-02-08 5:43 ` [PATCH 2/3] app/testpmd: add IPv6 flow label to RSS types Ajit Khaparde
2024-02-08 5:43 ` [PATCH 3/3] net/bnxt: add IPv6 flow label based RSS support Ajit Khaparde
2024-02-08 18:47 ` [PATCH 0/3] Support IPv6 flow label based RSS Ferruh Yigit
2024-02-08 18:56 ` Ajit Khaparde
2024-02-08 21:31 ` Ferruh Yigit
2024-02-08 22:06 ` [PATCH v2] ethdev: add support for RSS based on IPv6 flow label Ajit Khaparde
2024-02-08 22:22 ` Ferruh Yigit
2024-02-08 22:24 ` Ajit Khaparde
2024-02-09 18:16 ` [PATCH v3] " Ajit Khaparde
2024-02-09 22:45 ` Ferruh Yigit [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=9dfc174f-47a0-41bf-a32d-4100dc8a0ba0@amd.com \
--to=ferruh.yigit@amd.com \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--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).