netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yang Yingliang <yangyingliang@huawei.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: <stephen@networkplumber.org>, <netdev@vger.kernel.org>
Subject: Re: [PATCH iproute2] fq: don't allow set options to zero
Date: Mon, 12 May 2014 14:51:14 +0800	[thread overview]
Message-ID: <53706F62.2050603@huawei.com> (raw)
In-Reply-To: <1399874336.7973.17.camel@edumazet-glaptop2.roam.corp.google.com>

On 2014/5/12 13:58, Eric Dumazet wrote:
> On Mon, 2014-05-12 at 12:18 +0800, Yang Yingliang wrote:
>> Now options of fair queue can be zero but cannot be (~0U).
>> Zero is useless, so don't allow set the options to zero.
>> Also, maxrate cannot be reset to unlimited because it
>> cannot be (~0U).
>>
>> Cc: Eric Dumazet <edumazet@google.com>
>> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
>> ---
>>  tc/q_fq.c | 24 ++++++++++++------------
>>  1 file changed, 12 insertions(+), 12 deletions(-)
> 
> No, you are changing behavior for existing scripts.
> 
> If you really want to fix these cases, you need to do it properly.
> 

Do you mean allow options set to zero changing the behavior ?

Regards,
Yang

  reply	other threads:[~2014-05-12  6:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-12  4:18 [PATCH iproute2] fq: don't allow set options to zero Yang Yingliang
2014-05-12  5:58 ` Eric Dumazet
2014-05-12  6:51   ` Yang Yingliang [this message]
2014-05-12  6:55     ` Yang Yingliang
2014-05-12  6:59   ` Yang Yingliang
2014-05-12 15:23     ` Eric Dumazet
2014-05-13  2:23       ` [PATCH iproute2 v2] fq: allow options of fair queue set to ~0U Yang Yingliang
2014-05-13  3:03         ` Eric Dumazet
2014-05-13  4:10           ` Yang Yingliang
2014-05-13  4:20         ` [PATCH iproute2 v3] " Yang Yingliang
2014-05-29  0:09           ` Stephen Hemminger
2014-05-29  2:43             ` Yang Yingliang
2014-05-29  4:04             ` [PATCH iproute2 v4] " Yang Yingliang
2014-06-09 19:43               ` Stephen Hemminger

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=53706F62.2050603@huawei.com \
    --to=yangyingliang@huawei.com \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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).