From: "Dorsett, Michal" <Michal.Dorsett@verint.com>
To: "users@dpdk.org" <users@dpdk.org>
Cc: "Maimon, Royi" <Royi.Maimon@verint.com>
Subject: [dpdk-users] Round-robin instead of RSS
Date: Tue, 5 Dec 2017 21:23:23 +0000 [thread overview]
Message-ID: <DAC43FCF19B05149A1D1F5E9005F94F801359094E1@TLVMBX1.verint.corp.verintsystems.com> (raw)
We are using an XL710 nic 4x10Gbps.
Our application needs to delay all packets in the system for at least the first second, and depending on the type of traffic mbufs may need to delay packets even more.
Since the XL710 makes use of, at most, 1M mbufs in a queue and not more - we need to create several queues that provide enough mbufs for the nic not to starve.
Because we handle extremely varied traffic, we may not be able to statically configure an RSS to load balance traffic evenly between the queues.
Is it possible to set up a round-robin policy between the queues instead of RSS?
I realize the drawbacks - un-orderliness, etc. - but please assume we have our methods of handling those specific issues.
Thanks,
Michal Dorsett
Developer, Strategic IP Group
Desk: +972 962 4350
Mobile: +972 50 771 6689
Verint Cyber Intelligence
www.verint.com<http://www.verint.com/>
This electronic message may contain proprietary and confidential information of Verint Systems Inc., its affiliates and/or subsidiaries. The information is intended to be for the use of the individual(s) or entity(ies) named above. If you are not the intended recipient (or authorized to receive this e-mail for the intended recipient), you may not use, copy, disclose or distribute to anyone this message or any information contained in this message. If you have received this electronic message in error, please notify us by replying to this e-mail.
next reply other threads:[~2017-12-05 21:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 21:23 Dorsett, Michal [this message]
2017-12-05 22:34 ` Stephen Hemminger
2017-12-06 6:43 ` Dorsett, Michal
2017-12-06 23:05 ` Stephen Hemminger
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=DAC43FCF19B05149A1D1F5E9005F94F801359094E1@TLVMBX1.verint.corp.verintsystems.com \
--to=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).