CoDel AQM discussions
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: codel@lists.bufferbloat.net
Subject: [Codel] Fwd: [PATCH IPROUTE2] tc-codel: Add manpage
Date: Thu, 24 May 2012 06:27:40 +0100	[thread overview]
Message-ID: <CAA93jw7ySUYfRS83pokQQbZM06cvaUSSF6v-vw_COs1HF7zfpw@mail.gmail.com> (raw)
In-Reply-To: <1337835239.3361.3954.camel@edumazet-glaptop>

---------- Forwarded message ----------
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Thu, May 24, 2012 at 5:53 AM
Subject: Re: [PATCH IPROUTE2] tc-codel: Add manpage
To: Vijay Subramanian <subramanian.vijay@gmail.com>
Cc: netdev@vger.kernel.org, Stephen Hemminger <shemminger@vyatta.com>,
Dave Taht <dave.taht@gmail.com>


On Wed, 2012-05-23 at 21:33 -0700, Vijay Subramanian wrote:
> This patch adds the manpage for the CoDel (Controlled-Delay) AQM.
>
> Signed-off-by: Vijay Subramanian <subramanian.vijay@gmail.com>
> ---

Thanks !

> +.SS target
> +is the acceptable minimum standing/persistent queue delay. This minimum delay
> +is identified by tracking the local minimum queue delay that packets experience.
> +Default and recommended value is 5ms.

Although I can tell I prefer lower values on hosts.

On 10Gbe links, I used 500us target

> +
> +.SS interval
> +is used to ensure that the measured minimum delay does not become too stale. The
> +minimum delay must be experienced in the last epoch of length
> +.B interval.
> +It should be set on the order of the worst-case RTT through the bottleneck to
> +give endpoints sufficient time to react.  Default value is 100ms.

Same here. In a datacenter, you might reduce this to 20ms or so...





-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net

       reply	other threads:[~2012-05-24  5:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1337834034-27803-1-git-send-email-subramanian.vijay@gmail.com>
     [not found] ` <1337835239.3361.3954.camel@edumazet-glaptop>
2012-05-24  5:27   ` Dave Taht [this message]
2012-05-24  5:28 ` Dave Taht

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=CAA93jw7ySUYfRS83pokQQbZM06cvaUSSF6v-vw_COs1HF7zfpw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=codel@lists.bufferbloat.net \
    /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