From: Eric Dumazet <eric.dumazet@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>,
"Dave Täht" <dave.taht@bufferbloat.net>
Subject: Re: [Codel] [RFCv2 PATCH] codel: add ecn_target for when to drop rather than mark ecn packets
Date: Mon, 25 Jun 2012 20:51:18 +0200 [thread overview]
Message-ID: <1340650278.10893.93.camel@edumazet-glaptop> (raw)
In-Reply-To: <CAA93jw6s16EQbQSGFvBj9aJhgqW9FqLfL=b0hokNkum_TKfaVw@mail.gmail.com>
On Mon, 2012-06-25 at 11:25 -0700, Dave Taht wrote:
> On Mon, Jun 25, 2012 at 10:48 AM, Jonathan Morton <chromatix99@gmail.com> wrote:
> > My impression is that ECN ignorant flows do exist, because of stupid routers rather than malice, and that Dave considers this a problem worth tackling in codel.
>
> Malice will exist. It is easy to create a set of flows that will
> overwhelm either codel or fq_codel, with ecn enabled.
Then don't enable ecn. Simple.
Don't try to solve ecn problems at Qdisc layer, its not going to work.
fq_codel is default ecn enabled, because you can overwhelm fq_codel with
or without ecn anyway.
next prev parent reply other threads:[~2012-06-25 18:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 5:00 [Codel] [RFCv2 PATCH] iproute2: Add ecn_target option to codel and fq_codel 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 [this message]
2012-06-25 5:24 ` [Codel] [RFCv2 PATCH] iproute2: Add ecn_target option to codel and fq_codel Eric Dumazet
2012-06-25 5:29 ` 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=1340650278.10893.93.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=codel@lists.bufferbloat.net \
--cc=dave.taht@bufferbloat.net \
--cc=dave.taht@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