From: Filip Janiszewski <contact@filipjaniszewski.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Round-robin packet distribution
Date: Fri, 24 Jul 2020 12:05:34 +0200 [thread overview]
Message-ID: <9a39c4d5-8248-5223-df10-1c25fa1331c0@filipjaniszewski.com> (raw)
Hi,
Is there a way in DPDK to configure the NIC to distribute the incoming
packets to multiple queues in a round robin fashion? Without taking into
account the payload/headers or type of packet, just plain round robin
distribution to multiple queues.
I'm struggling to obtain a fair mechanism using RSS, perhaps the
rte_flow API can do the trick? Any other suggestion?
Thanks
--
BR, Filip
+48 666 369 823
next reply other threads:[~2020-07-24 10:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 10:05 Filip Janiszewski [this message]
2020-07-25 8:35 ` Tom Barbette
[not found] ` <8c8034d8-4cd5-bd0b-0958-14d08f5ae6e3@kth.se>
2020-08-18 12:40 ` Filip Janiszewski
2020-08-18 13:50 ` Pawel Wodkowski
2020-08-18 14:27 ` Filip Janiszewski
2020-08-24 10:08 ` Tom Barbette
[not found] ` <09498ac1-672d-a1e5-f917-d5720e1c90a7@kth.se>
2020-08-25 12:17 ` Pawel Wodkowski
2020-08-31 14:56 ` Filip Janiszewski
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=9a39c4d5-8248-5223-df10-1c25fa1331c0@filipjaniszewski.com \
--to=contact@filipjaniszewski.com \
--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).