From: John Fastabend <john.fastabend@gmail.com>
To: ivan <khorivan@gmail.com>, netdev@vger.kernel.org
Cc: kan.liang@intel.com, David Miller <davem@davemloft.net>
Subject: Re: [RFC] ethtool bandwidth per-queue commands
Date: Wed, 20 Jul 2016 18:06:19 -0700 [thread overview]
Message-ID: <5790200B.8000201@gmail.com> (raw)
In-Reply-To: <578FD85F.7080508@gmail.com>
On 16-07-20 01:00 PM, ivan wrote:
> Hi everyone.
>
> The ethtool interface has ETHTOOL_PERQUEUE command that is used to
> read/set per-queue parameters for multiqueue Ethernet devices.
>
> I want to apply additional per-queue commands like per-queue bandwidth
> and per-queue number of descriptors (like number of rings).
>
> Currently only ETHTOOL_G/SCOALESCE sub commands are added for
> per-queue interface (but I haven't seen counterpart for ethtool util).
>
> Using ETHTOOL_G/SCOALESCE per-queue command as an example,
> I'm going to add 2 additional and 2 known commands for ethtool
> per-queue interface:
>
> ETHTOOL_G/SBANDWIDTH /* Get/Set ethtool per queue bandwidth.
> Bandwidth can be set with % or absolute in Mb/s */
>
For tx rate limiting we have an ndo op for this already,
ndo_set_tx_maxrate
which can be tuned via sysfs at the moment. It would logically make
sense to add an rx rate limit if you are looking for something more
like a policer. Or do this via setup_tc() interface as we do with
mqprio qdisc today.
If you are interested in max and min rates per queue groups one such
possibility being a queue group of one you may find the ./net/dcb
stack interesting as well. Although the DCB spec has lots of bits
about protocols and such the kernel interfaces do not care if the
protocol is running at all. Unfortunately when this was done originally
we didn't make this as clear as we should have.
.John
prev parent reply other threads:[~2016-07-21 1:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 20:00 [RFC] ethtool bandwidth per-queue commands ivan
2016-07-20 20:51 ` Liang, Kan
2016-07-21 1:06 ` John Fastabend [this message]
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=5790200B.8000201@gmail.com \
--to=john.fastabend@gmail.com \
--cc=davem@davemloft.net \
--cc=kan.liang@intel.com \
--cc=khorivan@gmail.com \
--cc=netdev@vger.kernel.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).