From: Stephen Hemminger <stephen@networkplumber.org>
To: "Dorsett, Michal" <Michal.Dorsett@verint.com>
Cc: "users@dpdk.org" <users@dpdk.org>,
"Maimon, Royi" <Royi.Maimon@verint.com>,
"Heijmans, Merav" <Merav.Heijmans@verint.com>
Subject: Re: [dpdk-users] Round-robin instead of RSS
Date: Wed, 6 Dec 2017 15:05:11 -0800 [thread overview]
Message-ID: <20171206150511.75ba1d12@xeon-e3> (raw)
In-Reply-To: <DAC43FCF19B05149A1D1F5E9005F94F8013590954E@TLVMBX1.verint.corp.verintsystems.com>
On Wed, 6 Dec 2017 06:43:02 +0000
"Dorsett, Michal" <Michal.Dorsett@verint.com> wrote:
> I think my wording was not clear enough:
>
> Every packet that enters through the device will be delayed by our application for 1 second.
> Given 10Gbps worth of traffic, for example, at an average packet size of 600 bytes, this is roughly 2M packets per second.
>
> A 710-series NIC makes use of 1M mbufs in a queue at the very most. In order for us to delay 2M packets, we need to create several queues per NIC.
> I understand RSS is in the hardware, but hardware can be programmed, too, and hopefully turned off - and that's my question - whether, in addition to the RSS there is a round-robin policy that can be configured.
>
> Thanks,
>
> Michal
What I was suggesting is keep an internal ring buffer of packets.
Use a timer (rte_timer) to move the packets from ring buffer to device.
If you poll timer at 1000 hz, that would only be 2000 packets per interval.
The hardware queue can handle that.
RSS only matters on receive. You can dump any packet in any Tx queue.
On receive hardware supports:
* all packets on single queue
* packets spread across multiple queues by hash (RSS)
* packets directed to queue based on flow (a.ka. Flow Director).
next prev parent reply other threads:[~2017-12-06 23:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 21:23 Dorsett, Michal
2017-12-05 22:34 ` Stephen Hemminger
2017-12-06 6:43 ` Dorsett, Michal
2017-12-06 23:05 ` Stephen Hemminger [this message]
2017-12-07 7:43 ` Dorsett, Michal
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=20171206150511.75ba1d12@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=Merav.Heijmans@verint.com \
--cc=Michal.Dorsett@verint.com \
--cc=Royi.Maimon@verint.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).