From: Jonathan Morton <chromatix99@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>,
"bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Codel] [Bloat] Exploring the potential of codel, fq_codel, and qfq
Date: Wed, 16 May 2012 12:31:25 +0300 [thread overview]
Message-ID: <E26D25A9-315B-4003-A3DD-DBDE46781E45@gmail.com> (raw)
In-Reply-To: <1337159673.8512.1164.camel@edumazet-glaptop>
There are two goals here. One: provide real feedback to TCPs so that they know when the link is full and thus don't also fill up the buffer constantly. Two: prevent flows from unduly interfering with each other, so they don't have to fill the buffer just to be sure of good throughput.
What you seem to be saying is that you have a queue full of unresponsive flows that aren't being dropped because they have ECN support and are being marked instead. With FQ, that doesn't matter because other flows can still get through with low latency, and in fq_codel they are treated separately for mark/drop decision purposes. And if the queue really does fill up physically, codel already drops packets at head regardless of ECN capability.
The key to knowledge is not to rely on others to teach you it.
On 16 May 2012, at 12:14, Eric Dumazet <eric.dumazet@gmail.com> wrote:
> On Wed, 2012-05-16 at 12:02 +0300, Jonathan Morton wrote:
>> With FQ, I don't see what that would buy you.
>
> Sorry I dont understand your point.
>
next prev parent reply other threads:[~2012-05-16 9:31 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 1:04 [Codel] The challenge Dave Taht
2012-05-09 2:02 ` [Codel] [Bloat] " Kevin Gross
2012-05-09 3:13 ` [Codel] " Kathleen Nichols
2012-05-09 3:56 ` Dave Taht
2012-05-09 5:16 ` [Codel] [Bloat] " Simon Barber
2012-05-09 5:40 ` Eric Dumazet
2012-05-09 5:41 ` Dave Taht
2012-05-09 7:32 ` [Codel] [codel] some numbers on dual 10Gb links Eric Dumazet
2012-05-09 13:04 ` [Codel] [Bloat] The challenge Kevin Gross
2012-05-16 5:55 ` Jonathan Morton
2012-05-16 6:09 ` Eric Dumazet
2012-05-16 7:05 ` [Codel] Exploring the potential of codel, fq_codel, and qfq dave taht
2012-05-16 7:20 ` Dave Taht
2012-05-16 7:42 ` [Codel] [Bloat] " Eric Dumazet
2012-05-16 7:46 ` Eric Dumazet
2012-05-16 8:17 ` Eric Dumazet
2012-05-16 9:02 ` Jonathan Morton
2012-05-16 9:14 ` Eric Dumazet
2012-05-16 9:31 ` Jonathan Morton [this message]
2012-05-16 9:37 ` Eric Dumazet
2012-05-16 9:59 ` Jonathan Morton
2012-05-16 10:10 ` Eric Dumazet
2012-05-16 13:58 ` Eric Dumazet
2012-05-16 17:40 ` Rick Jones
2012-05-16 17:53 ` Eric Dumazet
2012-05-16 17:33 ` [Codel] " Rick Jones
2012-05-16 17:48 ` [Codel] [Bloat] " Eric Dumazet
2012-05-16 6:09 ` [Codel] [Bloat] The challenge Dave Taht
2012-05-16 6:31 ` Eric Dumazet
2012-05-16 8:15 ` Jonathan Morton
2012-05-09 19:10 ` Roger Jørgensen
2012-05-09 19:15 ` Dave Taht
2012-05-09 19:28 ` Dave Taht
2012-05-09 20:02 ` Simon Barber
2012-05-09 20:06 ` Fred Baker
2012-05-09 21:47 ` Jim Gettys
2012-05-09 23:58 ` Eric Dumazet
2012-05-10 2:34 ` Jonathan Morton
2012-05-10 2:37 ` Dave Taht
2012-05-10 6:35 ` David Woodhouse
2012-05-10 6:54 ` Jonathan Morton
2012-05-10 7:02 ` David Woodhouse
2012-05-10 14:25 ` Justin McCann
2012-05-10 14:42 ` David Woodhouse
2012-05-10 15:34 ` Neil Davies
2012-05-10 21:20 ` Jim Gettys
2012-05-14 7:27 ` Jonathan Morton
2012-05-14 7:34 ` Eric Dumazet
2012-05-14 13:55 ` David Woodhouse
2012-05-18 20:56 ` [Codel] [Bloat] Linux-able modems Jonathan Morton
2012-05-18 21:36 ` Dave Taht
2012-05-18 22:34 ` 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=E26D25A9-315B-4003-A3DD-DBDE46781E45@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--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