netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yang Yingliang <yangyingliang@huawei.com>
To: Duan Jiong <duanj.fnst@cn.fujitsu.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] sch_tbf: add TBF_BURST/TBF_PBURST attribute
Date: Mon, 16 Dec 2013 10:11:59 +0800	[thread overview]
Message-ID: <52AE616F.9050001@huawei.com> (raw)
In-Reply-To: <52AAD867.5030305@cn.fujitsu.com>

On 2013/12/13 17:50, Duan Jiong wrote:
> 于 2013年12月13日 17:41, Yang Yingliang 写道:
>> When we set burst to 1514 with low rate in userspace,
>> the kernel get a value of burst that less than 1514,
>> which doesn't work.
>>
>> Because it may make some loss when transform burst
>> to buffer in userspace. This makes burst lose some
>> bytes, when the kernel transform the buffer back to
>> burst.
>>
>> This patch adds two new attributes to support sending
>> burst/mtu to kernel directly to avoid the loss.
>>
>> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
>> ---
[...]
>> diff --git a/net/sched/sch_tbf.c b/net/sched/sch_tbf.c
>> index 887e672..a746049 100644
>> --- a/net/sched/sch_tbf.c
>> +++ b/net/sched/sch_tbf.c
>> @@ -307,6 +307,8 @@ static const struct nla_policy tbf_policy[TCA_TBF_MAX + 1] = {
>>  	[TCA_TBF_PTAB]	= { .type = NLA_BINARY, .len = TC_RTAB_SIZE },
>>  	[TCA_TBF_RATE64]	= { .type = NLA_U64 },
>>  	[TCA_TBF_PRATE64]	= { .type = NLA_U64 },
>> +	[TCA_TBF_BURST]		= { .type = NLA_U32 },
> 
> This place should remove one tab.
> 
> Thanks,
>   Duan
> 

OK, thanks!

  reply	other threads:[~2013-12-16  2:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-13  9:41 [PATCH net-next] sch_tbf: add TBF_BURST/TBF_PBURST attribute Yang Yingliang
2013-12-13  9:50 ` Duan Jiong
2013-12-16  2:11   ` Yang Yingliang [this message]
2013-12-17  3:34 ` [PATCH resend " Yang Yingliang
2013-12-19 20:03   ` David Miller
2013-12-19 20:15   ` Eric Dumazet
2013-12-20  1:24     ` [PATCH v3 " Yang Yingliang
2013-12-20  1:31       ` Eric Dumazet
2013-12-26 18:54       ` David Miller

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=52AE616F.9050001@huawei.com \
    --to=yangyingliang@huawei.com \
    --cc=duanj.fnst@cn.fujitsu.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).