From: Stephen Hemminger <stephen@networkplumber.org>
To: Raghavan V <Raghavan.V2@tatacommunications.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: FDIR packet distribution with specific multiple RX queues.
Date: Thu, 18 Jul 2024 08:36:07 -0700 [thread overview]
Message-ID: <20240718083607.2b70d734@hermes.local> (raw)
In-Reply-To: <TYZPR04MB54167C8310DB1191A38631F3C8AC2@TYZPR04MB5416.apcprd04.prod.outlook.com>
On Thu, 18 Jul 2024 11:36:43 +0000
Raghavan V <Raghavan.V2@tatacommunications.com> wrote:
> Is there any way to distribute packets evenly (Like RSS) to specific multiple RX queues in RTE_FLOW_ACTION_TYPE_QUEUE DPDK Flow director?
>
> Desired action:
>
> uint16_t queue_indices[] = {10, 11, 12, 13, 14, 15};
> struct rte_flow_action_queue queue = {.index = queue_indices};
> struct rte_flow_action action[]={
> [0]={.type = RTE_FLOW_ACTION_TYPE_QUEUE,.conf = &queue},
> [1]={.type = RTE_FLOW_ACTION_TYPE_END}
> };
You want RTE_FLOW_ACTION_TYPE_RSS
uint16_t queue_indices[] = {10, 11, 12, 13, 14, 15};
struct rte_flow_action_rss rss = {
.types = RTE_ETH_RSS_UDP | RTE_ETH_RSS_TCP,
.queue_num = RTE_DIM(queue_indicies),
.queue = queue_indicies,
};
struct rte_flow_action action[]={
[0]={.type = RTE_FLOW_ACTION_TYPE_RSS,.conf = &rss},
[1]={.type = RTE_FLOW_ACTION_TYPE_END}
};
> Is this action limited to drivers specific?
Yes, drivers implement only what hardware can support.
next prev parent reply other threads:[~2024-07-18 15:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 11:36 FDIR packet distribution with specific multiple RX queues Raghavan V
2024-07-18 15:36 ` Stephen Hemminger [this message]
2024-07-18 16:39 ` Raghavan V
2024-07-18 17:28 ` 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=20240718083607.2b70d734@hermes.local \
--to=stephen@networkplumber.org \
--cc=Raghavan.V2@tatacommunications.com \
--cc=dev@dpdk.org \
--cc=users@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.