Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: ecn-sane@lists.bufferbloat.net
Subject: Re: [Ecn-sane] robustness against attack?
Date: Mon, 25 Mar 2019 16:23:35 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1903251619580.3161@uplift.swm.pp.se> (raw)
In-Reply-To: <907D3152-4AD5-4551-AA6A-46FF9CA567DE@gmail.com>

On Mon, 25 Mar 2019, Jonathan Morton wrote:

>> On 25 Mar, 2019, at 8:16 am, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>>
>> Do people on this email list think we're trying to trick you when we're saying that FQ won't be available anytime soon on a lot of platforms that need this kind of AQM?
>
> Well, I don't.  I recognise that most high-capacity links will end up 
> with single-queue AQM, because that's what's already out there in 
> hardware (though it's rarely turned on so far).  I'm still keen to see 
> good FQ used where feasible, and in ways that make local sense.

Ok, so can we please drop the "FQ" part of the conversation for the next 
months, and argue on few-queue systems and how to come up with things that 
are friendly to implement in hardware?

Just to state again what I have said several times:

Devices such as high speed residential gateways, BNGs, CMTSs etc, they 
will not get FQ anytime in the next 5-10 years (or someone will have to 
prove me wrong).

So please stop arguing about the wonderfulness of FQ. Yes, fine, it's 
great, but it's also not applicable to lots of places where we need to 
de-bloat.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

  parent reply	other threads:[~2019-03-25 15:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-24 22:50 Sebastian Moeller
2019-03-25  7:16 ` Mikael Abrahamsson
2019-03-25  7:54   ` [Ecn-sane] FQ in the core Dave Taht
2019-03-25  9:17     ` Luca Muscariello
2019-03-25  9:52       ` Sebastian Moeller
2019-03-25  9:23     ` Sebastian Moeller
2019-03-25 15:43     ` Mikael Abrahamsson
2019-03-25  8:34   ` [Ecn-sane] robustness against attack? Jonathan Morton
2019-03-25  8:53     ` Jonathan Morton
2019-03-25  9:40       ` Sebastian Moeller
2019-03-25 15:23     ` Mikael Abrahamsson [this message]
2019-03-25 22:53       ` David P. Reed
2019-03-25  8:46   ` Sebastian Moeller

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/ecn-sane.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.20.1903251619580.3161@uplift.swm.pp.se \
    --to=swmike@swm.pp.se \
    --cc=chromatix99@gmail.com \
    --cc=ecn-sane@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