From: Rick Jones <rick.jones2@hp.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Eric Dumazet <edumazet@google.com>,
codel@lists.bufferbloat.net,
Dave Taht <dave.taht@bufferbloat.net>
Subject: Re: [Codel] [PATCH 1/2] codel: Controlled Delay AQM
Date: Mon, 07 May 2012 10:27:21 -0700 [thread overview]
Message-ID: <4FA805F9.20004@hp.com> (raw)
In-Reply-To: <1336410626.3752.2329.camel@edumazet-glaptop>
On 05/07/2012 10:10 AM, Eric Dumazet wrote:
> On Mon, 2012-05-07 at 09:43 -0700, Rick Jones wrote:
>> On 05/05/2012 12:32 PM, Dave Taht wrote:
>>> From: Dave Täht<dave.taht@bufferbloat.net>
>>>
>>> tc qdisc ... codel [ limit PACKETS ] [ target TIME]
>>> [ interval TIME ] [ minbytes BYTES ]
>>
>> Usability suggestions - "target_latency" or "target_lat" and
>> "action_interval" or "decision_interval" perhaps?
>
> We took the terms used in the codel paper.
>
> By the way, target is not target_latency, its more a target threshold
> (packets under it are not dropped), but packets above might be dropped.
I don't wish to rathole, and someone may want to declare Bikeshed! but
the target audience of the paper is a bit different from the Linux
system administrator base yes? If a parameter name enhancement makes
something more clear to an administrator is it really a bad thing to
have a name that is not a strict duplicate of the paper's?
rick
next prev parent reply other threads:[~2012-05-07 17:27 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-05 19:32 Dave Taht
2012-05-05 19:32 ` [Codel] [PATCH 2/2] codel: RED is dead Dave Taht
2012-05-05 19:47 ` [Codel] [PATCH 1/2] codel: Controlled Delay AQM Dave Taht
2012-05-05 20:05 ` Eric Dumazet
2012-05-07 16:43 ` Rick Jones
2012-05-07 17:10 ` Eric Dumazet
2012-05-07 17:18 ` Dave Taht
2012-05-07 17:27 ` Rick Jones [this message]
2012-05-07 17:34 ` Eric Dumazet
2012-05-07 17:52 ` Dave Taht
2012-05-07 18:01 ` Eric Dumazet
2012-05-07 18:09 ` Eric Dumazet
2012-05-07 18:15 ` Eric Dumazet
2012-05-07 18:32 ` Jim Gettys
2012-05-07 18:44 ` Dave Taht
2012-05-07 18:50 ` Jim Gettys
2012-05-07 19:16 ` Eric Dumazet
2012-05-07 19:36 ` Jim Gettys
2012-05-07 20:03 ` Eric Dumazet
2012-05-07 20:55 ` dave taht
2012-05-08 1:15 ` Jim Gettys
2012-05-08 1:20 ` Andrew McGregor
2012-05-08 1:45 ` Jim Gettys
2012-05-08 2:16 ` Rick Jones
2012-05-08 3:14 ` Jim Gettys
2012-05-08 3:32 ` Rick Jones
2012-05-08 3:40 ` Kathleen Nichols
2012-05-08 4:14 ` Jim Gettys
2012-05-08 5:10 ` Eric Dumazet
2012-05-08 10:25 ` Jim Gettys
2012-05-08 13:57 ` Kathleen Nichols
2012-05-08 14:04 ` Jim Gettys
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
List information: https://lists.bufferbloat.net/postorius/lists/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FA805F9.20004@hp.com \
--to=rick.jones2@hp.com \
--cc=codel@lists.bufferbloat.net \
--cc=dave.taht@bufferbloat.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.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