From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Dave Täht" <dave.taht@bufferbloat.net>
Cc: codel@lists.bufferbloat.net
Subject: Re: [Codel] [RFCv2 PATCH] iproute2: Add ecn_target option to codel and fq_codel
Date: Mon, 25 Jun 2012 07:24:22 +0200 [thread overview]
Message-ID: <1340601862.23933.18.camel@edumazet-glaptop> (raw)
In-Reply-To: <1340600422-1806-1-git-send-email-dave.taht@bufferbloat.net>
On Sun, 2012-06-24 at 22:00 -0700, Dave Täht wrote:
> From: Dave Taht <dave.taht@bufferbloat.net>
>
> ECN was not part of the original codel design and adding support
> for it revealed problems in two areas. 1) ECN can be gamed.
> 2) Dropping packets under overload more rapidly frees up
> bandwidth than marking packets.
>
> Two possible scenarios of use - on egress from a network,
> ecn_target could be set low, to drop more often, to
> ensure lowest latency for other packets.
>
> On ingress, it could be set high to mark packets more often,
> to lower data loss while still signalling the end application
> that bandwidth is a problem.
>
> ecn_target is not engaged until after codel enters a dropping
> state overall.
> ---
> include/linux/pkt_sched.h | 2 ++
> man/man8/tc-codel.8 | 3 +++
> man/man8/tc-fq_codel.8 | 5 +++++
> tc/q_codel.c | 17 ++++++++++++++++-
> tc/q_fq_codel.c | 17 ++++++++++++++++-
> 5 files changed, 42 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/pkt_sched.h b/include/linux/pkt_sched.h
> index 32aef0a..f0dcf8c 100644
> --- a/include/linux/pkt_sched.h
> +++ b/include/linux/pkt_sched.h
> @@ -663,6 +663,7 @@ enum {
> TCA_CODEL_LIMIT,
> TCA_CODEL_INTERVAL,
> TCA_CODEL_ECN,
> + TCA_CODEL_ECN_TARGET,
> __TCA_CODEL_MAX
> };
>
> @@ -691,6 +692,7 @@ enum {
> TCA_FQ_CODEL_ECN,
> TCA_FQ_CODEL_FLOWS,
> TCA_FQ_CODEL_QUANTUM,
> + TCA_FQ_CODEL_ECN_TARGET,
> __TCA_FQ_CODEL_MAX
> };
>
> diff --git a/man/man8/tc-codel.8 b/man/man8/tc-codel.8
> index 61f163f..0e97249 100644
> --- a/man/man8/tc-codel.8
> +++ b/man/man8/tc-codel.8
> @@ -64,6 +64,9 @@ 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.
>
> +.SS ecn_target
> +is the overall delay at which ecn marked packets will be dropped rather than marked.
> +
> .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
> diff --git a/man/man8/tc-fq_codel.8 b/man/man8/tc-fq_codel.8
> index 8b43c10..9cb5be8 100644
> --- a/man/man8/tc-fq_codel.8
> +++ b/man/man8/tc-fq_codel.8
> @@ -49,6 +49,11 @@ and is the acceptable minimum
> standing/persistent queue delay. This minimum delay is identified by tracking
> the local minimum queue delay that packets experience. Default value is 5ms.
>
> +.SS ecn_target
> +has the same semantics as
> +.B codel
> +and is the delay beyond which ecn packets will be dropped rather than marked.
> +
What do you mean by "ecn_target has the same semantics as codel" ?
next prev parent reply other threads:[~2012-06-25 5:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 5:00 Dave Täht
2012-06-25 5:00 ` [Codel] [RFCv2 PATCH] codel: add ecn_target for when to drop rather than mark ecn packets Dave Täht
2012-06-25 5:22 ` Eric Dumazet
2012-06-25 14:50 ` Dave Taht
2012-06-25 15:20 ` Eric Dumazet
2012-06-25 15:30 ` Dave Taht
2012-06-25 15:45 ` Eric Dumazet
2012-06-25 17:48 ` Jonathan Morton
2012-06-25 18:25 ` Dave Taht
2012-06-25 18:51 ` Eric Dumazet
2012-06-25 5:24 ` Eric Dumazet [this message]
2012-06-25 5:29 ` [Codel] [RFCv2 PATCH] iproute2: Add ecn_target option to codel and fq_codel Eric Dumazet
2012-06-25 14:54 ` 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=1340601862.23933.18.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=codel@lists.bufferbloat.net \
--cc=dave.taht@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