From: Paul Emmerich <emmericp@net.in.tum.de>
To: dev@dpdk.org
Subject: [dpdk-dev] Per-queue bandwidth limit on XL710 NICs?
Date: Mon, 15 Feb 2016 18:34:51 +0100 [thread overview]
Message-ID: <56C20C3B.8030403@net.in.tum.de> (raw)
Hi,
I'm using the per-queue rate control feature found in ixgbe-style NICs
(rte_eth_set_queue_rate_limit) quite extensively in my packet generator
MoonGen.
I've read some parts of the XL710 datasheet and I guess it should be
possible to implement this for this chip. I think there are two ways to
achieves this:
1) Limiting the main VSI and thus the whole port by calling
i40e_aq_config_vsi_bw_limit() in the driver works fine. Thus, creating
multiple VSIs for each rate-controlled queue would be a possible solution.
I'm not sure if that works without major modifications to the driver. I
probably need a VEB for that which currently isn't supported in the driver.
2) Use multiple TCs for the used VSI. That would limit us to 8 rate
limits but that would be okay. Probably the simpler solution.
Can anyone with more insight into the XL710 hardware give me some hints
on implementing this?
Paul
reply other threads:[~2016-02-15 17:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=56C20C3B.8030403@net.in.tum.de \
--to=emmericp@net.in.tum.de \
--cc=dev@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).