Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: ecn-sane@lists.bufferbloat.net
Subject: Re: [Ecn-sane] robustness against attack?
Date: Mon, 25 Mar 2019 08:16:43 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1903250810490.3161@uplift.swm.pp.se> (raw)
In-Reply-To: <3E9C6E74-E335-472B-8745-6020F7CDBA01@gmx.de>

On Sun, 24 Mar 2019, Sebastian Moeller wrote:

> From my layman's perspective this is the the killer argument against the 
> dualQ approach and for fair-queueing, IMHO only fq will be able to

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?

Since there is always demand for implementations, can we get an ASIC/NPU 
implementation of FQ_CODEL done by someone who claims it's no problem?

Personally I believe we need both. FQ is obviously superior to anything 
else most of the time, but FQ is not making itself into the kind of 
devices it needs to get into for the bufferbloat situation to improve, so 
now what?

Claiming to have a superior solution that is too expensive to go into 
relevant devices, is that proposal still relevant as an alternative to a 
different solution that actually is making itself into silicon?

Again, FQ superior, but what what good is it if it's not being used?

We need to have this discussion and come up with a joint understanding of 
the world, otherwise we're never going to get anywhere.

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

  reply	other threads:[~2019-03-25  7:16 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 [this message]
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
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.1903250810490.3161@uplift.swm.pp.se \
    --to=swmike@swm.pp.se \
    --cc=ecn-sane@lists.bufferbloat.net \
    --cc=moeller0@gmx.de \
    /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