From: Stephen Hemminger <stephen@networkplumber.org>
To: Amritha Nambiar <amritha.nambiar@intel.com>
Cc: netdev@vger.kernel.org, alexander.h.duyck@intel.com,
kiran.patil@intel.com, sridhar.samudrala@intel.com,
mitch.a.williams@intel.com, alexander.duyck@gmail.com,
neerav.parikh@intel.com, carolyn.wyborny@intel.com,
jeffrey.t.kirsher@intel.com
Subject: Re: [PATCH RFC, iproute2] tc/mqprio: Add support to configure bandwidth rate limit through mqprio
Date: Tue, 18 Jul 2017 17:29:35 -0700 [thread overview]
Message-ID: <20170718172935.6426dc6c@xeon-e3> (raw)
In-Reply-To: <150008197300.6559.15065389482024982399.stgit@anamdev.jf.intel.com>
On Fri, 14 Jul 2017 18:26:13 -0700
Amritha Nambiar <amritha.nambiar@intel.com> wrote:
> Support bandwidth rate limit information for a traffic
> class in addition to the number of TCs and associated
> queue configuration data. This is supported in the new
> hardware offload mode in mqprio by setting the value of
> 'hw' option to 2. This new hardware offload mode in mqprio
> makes full use of the mqprio options, the TCs, the
> queue configurations and the bandwidth rates for the TCs.
>
> # tc qdisc add dev eth0 root mqprio num_tc 2 map 0 0 0 0 1 1 1 1\
> queues 4@0 4@4 min_rate 0Mbit 0Mbit max_rate 55Mbit 60Mbit hw 2
>
> # tc qdisc show dev eth0
>
> qdisc mqprio 804a: root tc 2 map 0 0 0 0 1 1 1 1 0 0 0 0 0 0 0 0
> queues:(0:3) (4:7)
> min rates:0bit 0bit
> max rates:55Mbit 60Mbit
>
> Signed-off-by: Amritha Nambiar <amritha.nambiar@intel.com>
As Jamal said, the syntax is awquard.
Also, for iproute2 commands the output format should match the input format
prev parent reply other threads:[~2017-07-19 0:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-15 1:26 [PATCH RFC, iproute2] tc/mqprio: Add support to configure bandwidth rate limit through mqprio Amritha Nambiar
2017-07-19 0:29 ` Stephen Hemminger [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=20170718172935.6426dc6c@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=alexander.duyck@gmail.com \
--cc=alexander.h.duyck@intel.com \
--cc=amritha.nambiar@intel.com \
--cc=carolyn.wyborny@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=kiran.patil@intel.com \
--cc=mitch.a.williams@intel.com \
--cc=neerav.parikh@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sridhar.samudrala@intel.com \
/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).