From: Stephen Hemminger <stephen@networkplumber.org>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: <netdev@vger.kernel.org>, <eric.dumazet@gmail.com>
Subject: Re: [PATCH iproute2] tbf: add 64bit rates support
Date: Mon, 2 Dec 2013 23:52:55 -0800 [thread overview]
Message-ID: <20131202235255.3d1fb74f@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1385430935-19740-1-git-send-email-yangyingliang@huawei.com>
On Tue, 26 Nov 2013 09:55:35 +0800
Yang Yingliang <yangyingliang@huawei.com> wrote:
> tbf support 64bit rates start from linux-3.13.
> Add 64bit rates support in tc tools.
>
> tc qdisc show dev eth0
> qdisc tbf 1: root refcnt 2 rate 40000Mbit burst 230000b peakrate 50000Mbit minburst 87500b lat 50.0ms
>
> This is a followup to ("htb: support 64bit rates").
>
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
> Cc: Eric Dumazet <edumazet@google.com>
Queued in net-next-for-3.13; since it does not build against 3.13-rc2
prev parent reply other threads:[~2013-12-03 7:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 1:55 [PATCH iproute2] tbf: add 64bit rates support Yang Yingliang
2013-12-03 7:52 ` 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=20131202235255.3d1fb74f@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=yangyingliang@huawei.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).