From: Tom Barbette <barbette@kth.se>
To: Filip Janiszewski <contact@filipjaniszewski.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Round-robin packet distribution
Date: Sat, 25 Jul 2020 10:35:00 +0200 [thread overview]
Message-ID: <cf04f799-a92a-137f-b079-a42e7987dc9e@kth.se> (raw)
In-Reply-To: <9a39c4d5-8248-5223-df10-1c25fa1331c0@filipjaniszewski.com>
Hi Filip,
This is not possible, but you may use the idea of Sprayer
(http://www.gta.ufrj.br/ftp/gta/TechReports/SCC18d.pdf) to dispatch
packets randomly (use RSS on the checksum).
However, in our paper RSS++
(https://www.diva-portal.org/smash/get/diva2:1371780/FULLTEXT01.pdf) we
show it's nearly always a bad idea because you'll have to share state,
and even for "stateless" function, that leads to a very bad locality in
a firewall as the same rules have to be fetched to L1 to all cores at
the same time when you receive a burst of similar packets.
Tom
Le 24/07/2020 à 12:05, Filip Janiszewski a écrit :
> 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
>
next prev parent reply other threads:[~2020-07-25 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 10:05 Filip Janiszewski
2020-07-25 8:35 ` Tom Barbette [this message]
[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=cf04f799-a92a-137f-b079-a42e7987dc9e@kth.se \
--to=barbette@kth.se \
--cc=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).