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 10:28:46 -0700 [thread overview]
Message-ID: <20240718102846.4940cff3@hermes.local> (raw)
In-Reply-To: <TYZPR04MB54169EAD13C7C52D90030134C8AC2@TYZPR04MB5416.apcprd04.prod.outlook.com>
On Thu, 18 Jul 2024 16:39:35 +0000
Raghavan V <Raghavan.V2@tatacommunications.com> wrote:
> Hi Stephen,
> Thanks for your response.
>
> As our application has limitations while using RSS,
> I would prefer a similar approach to RTE_ACTION_TYPE_QUEUE.
There is no action like this since hardware does not support it.
Multi queue support comes from the original queue support which was
done as collaboration between Intel and Microsoft (for Windows).
Then Linux got multi-queue (RSS) support.
Then DPDK got similar multi-queue.
Packet spraying across queues would be bad since it would create
out of order packets, and also lots of lock contention on any shared
per flow resource.
prev parent reply other threads:[~2024-07-18 17:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 11:36 Raghavan V
2024-07-18 15:36 ` Stephen Hemminger
2024-07-18 16:39 ` Raghavan V
2024-07-18 17:28 ` 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=20240718102846.4940cff3@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 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).