From: Yang Yingliang <zjutyyl@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>,
Yang Yingliang <yangyingliang@huawei.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, brouer@redhat.com,
jpirko@redhat.com, jbrouer@redhat.com
Subject: Re: [PATCH net v3 1/2] net: sched: tbf: fix calculation of max_size
Date: Sun, 24 Nov 2013 15:28:13 +0800 [thread overview]
Message-ID: <5291AA8D.6060108@gmail.com> (raw)
In-Reply-To: <1385233579.10637.95.camel@edumazet-glaptop2.roam.corp.google.com>
On 2013/11/24 3:06, Eric Dumazet wrote:
> On Tue, 2013-11-19 at 15:25 +0800, Yang Yingliang wrote:
>> commit b757c9336d63f94c6b57532(tbf: improved accuracy at high rates)
>> introduce a regression.
>>
>> With the follow command:
>> tc qdisc add dev eth1 root handle 1: tbf latency 50ms burst 10KB rate 30gbit mtu 64k
>>
>> Without this patch, the max_size value is 10751(bytes).
>> But, in fact, the real max_size value should be smaller than 7440(bytes).
>> Or a packet whose length is bigger than 7440 will cause network congestion.
>> Because the packet is so big that can't get enough tokens. Even all the tokens
>> in the buffer is given to the packet.
>>
>> With this patch, the max_size value is 7440(bytes).
>> The packets whose length is bigger than 7440(bytes) will be dropped or reshape
>> in tbf_enqueue().
> This changelog makes no sense.
>
> If userland asks 'burst 10KB', then burst is 10KB, not 7440.
>
Ideally burst should be 10KB in kernel space.
But at hight rates, when burst is converted to
time in tick in userland, it gets much more loss
than low rates. So the burst can't actually
reach 10KB in kernel.
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-11-24 7:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 7:25 [PATCH net v3 0/2] net: sched: fix some issues Yang Yingliang
2013-11-19 7:25 ` [PATCH net v3 1/2] net: sched: tbf: fix calculation of max_size Yang Yingliang
2013-11-19 9:38 ` Jesper Dangaard Brouer
2013-11-20 2:14 ` Yang Yingliang
2013-11-20 10:04 ` Jesper Dangaard Brouer
2013-11-20 12:50 ` Yang Yingliang
2013-11-23 19:06 ` Eric Dumazet
2013-11-24 7:28 ` Yang Yingliang [this message]
2013-11-24 18:40 ` Eric Dumazet
2013-11-25 3:43 ` Yang Yingliang
2013-11-25 12:04 ` [PATCH] " Yang Yingliang
2013-11-25 12:22 ` David Laight
2013-11-26 1:28 ` Yang Yingliang
2013-11-26 2:35 ` Yang Yingliang
2013-12-02 1:11 ` David Miller
2013-12-02 10:29 ` David Laight
2013-12-02 16:45 ` David Miller
2013-12-03 0:59 ` Yang Yingliang
2013-11-19 7:25 ` [PATCH net v3 2/2] net: sched: htb: fix calculation of quantum Yang Yingliang
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=5291AA8D.6060108@gmail.com \
--to=zjutyyl@gmail.com \
--cc=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jbrouer@redhat.com \
--cc=jpirko@redhat.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).