From: Yang Yingliang <yangyingliang@huawei.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: <davem@davemloft.net>, <netdev@vger.kernel.org>,
<brouer@redhat.com>, <jpirko@redhat.com>, <jbrouer@redhat.com>
Subject: Re: [PATCH net v4 1/2] net: sched: tbf: fix calculation of max_size
Date: Wed, 4 Dec 2013 09:53:02 +0800 [thread overview]
Message-ID: <529E8AFE.30906@huawei.com> (raw)
In-Reply-To: <1386082293.30495.26.camel@edumazet-glaptop2.roam.corp.google.com>
On 2013/12/3 22:51, Eric Dumazet wrote:
> On Tue, 2013-12-03 at 19:32 +0800, Yang Yingliang wrote:
>
>>>
>>>>
>>>> TSO packet of 64KB -> about 45 frames if MSS=1448, 45*1514 = 68130 bytes
>>
>> Maybe MAX_PKT_LEN should be much bigger. Hmm, I'm uncertain how big is the proper value.
>>
>
> Thats the thing : When user is able to compute the appropriate burst and
> give precise instructions to the kernel, why tbf would reduce it to
> whatever fixed threshold ?
>
> If I set 200000 as a burst, I do not want tbf use 65536 or even less.
>
> If tbf rounds my 200000 to 199800, its fine.
>
> You had problems to set burst to appropriate values, but most other
> users did that fine.
>
> tbf_segment() is an attempt to help for very low rates, to not overcome
> the small bursts (as low as 2000 bytes) programmed on atbf qdisc, but
> for high rates, we _definitely_ want to avoid segmentation as hell.
>
Thanks for your opinions!
>From your opinions, how about calculating burst directly with q->buffer and psched_ns_t2l().
I did it in my v1 patch:
/* Time to Length, convert time in ns to length in bytes
* to determinate how many bytes can be sent in given time.
*/
static inline u64 psched_ns_t2l(const struct psched_ratecfg *r,
u64 time_in_ns)
{
u64 len = time_in_ns;
u8 shift = r->shift;
bool is_div = false;
/* The formula is :
* len = (time_in_ns << shift) / mult
* when time_in_ns does shift, it would overflow.
* If overflow happens first time, do division.
* Then do shift. If it happens again,
* set lenth to ~0ULL.
*/
while (shift) {
if (len & (1ULL << 63)) {
if (!is_div) {
len = div64_u64(len, r->mult);
is_div = true;
} else {
/* overflow happens */
len = ~0ULL;
is_div = true;
break;
}
}
len <<= 1;
shift--;
}
if (!is_div)
len = div64_u64(len, r->mult);
if (unlikely(r->linklayer == TC_LINKLAYER_ATM))
len = (len / 53) * 48;
if (len > r->overhead)
len -= r->overhead;
else
len = 0;
return len;
}
max_size = min_t(u64, psched_ns_t2l(&q->rate, q->buffer), ~0);
Regards,
Yang
next prev parent reply other threads:[~2013-12-04 1:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 3:26 [PATCH net v4 0/2] net: sched: fix some issues Yang Yingliang
2013-12-03 3:26 ` [PATCH net v4 1/2] net: sched: tbf: fix calculation of max_size Yang Yingliang
2013-12-03 4:51 ` Eric Dumazet
2013-12-03 6:09 ` Yang Yingliang
2013-12-03 4:59 ` Eric Dumazet
2013-12-03 7:44 ` Yang Yingliang
2013-12-03 8:12 ` Eric Dumazet
2013-12-03 9:47 ` Yang Yingliang
2013-12-03 11:32 ` Yang Yingliang
2013-12-03 14:51 ` Eric Dumazet
2013-12-04 1:53 ` Yang Yingliang [this message]
2013-12-03 3:26 ` [PATCH net v4 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=529E8AFE.30906@huawei.com \
--to=yangyingliang@huawei.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 \
/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).