From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht <dave@taht.net>
Cc: "ecn-sane@lists.bufferbloat.net" <ecn-sane@lists.bufferbloat.net>,
"tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: [Ecn-sane] is FQ actually widely deployed?
Date: Mon, 22 Jul 2019 16:14:22 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1907221609330.19225@uplift.swm.pp.se> (raw)
On Fri, 19 Jul 2019, Dave Taht wrote:
> In particular conflating "low latency" really confounds the subject
> matter, and has for years. FQ gives "low latency" for the vast
> majority of flows running below their fair share. L4S promises "low
My observations from the business is that FQ just isn't a thing, in
reality.
I run CAKE myself here on my OpenWrt box and it works great, but I have
yet to find a commercially available box used by ISPs or something that is
a big-seller in electronics stores that use FQ_anything, or is even flow
aware when it comes to forwarding.
I have heard nothing about FQ being implemented in packet accelerators. I
do hear about people wanting to turn on things that control delay/buffer
fill, but this is still single queue with no flow-aware anything.
Do we have numbers on how much FQ is actually out there? If we don't, can
we measure it? Anyone know of devices shipping or being designed that does
FQ of some kind?
--
Mikael Abrahamsson email: swmike@swm.pp.se
next reply other threads:[~2019-07-22 14:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 14:14 Mikael Abrahamsson [this message]
2019-07-22 15:20 ` Jonathan Morton
2019-07-22 17:05 ` Toke Høiland-Jørgensen
2019-07-22 18:02 ` Pete Heist
2019-07-23 5:32 ` Mikael Abrahamsson
2019-07-23 5:57 ` Sebastian Moeller
2019-07-23 6:06 ` Jonathan Morton
2019-07-22 22:14 ` Jonathan Foulkes
2019-07-22 22:24 ` Jonathan Morton
2019-07-22 17:09 ` Dave Taht
2019-07-23 5:34 ` Mikael Abrahamsson
2019-07-23 6:13 ` Sebastian Moeller
2019-07-23 6:21 ` Mikael Abrahamsson
2019-07-23 10:57 ` 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/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.1907221609330.19225@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=dave@taht.net \
--cc=ecn-sane@lists.bufferbloat.net \
--cc=tsvwg@ietf.org \
/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