From: Sebastian Moeller <moeller0@gmx.de>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"Jonathan Foulkes" <jfoulkes@evenroute.com>,
"ecn-sane@lists.bufferbloat.net" <ecn-sane@lists.bufferbloat.net>,
"Dave Taht" <dave@taht.net>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [Ecn-sane] is FQ actually widely deployed?
Date: Tue, 23 Jul 2019 07:57:14 +0200 [thread overview]
Message-ID: <BAC8C466-E215-46AE-9D30-591A82055633@gmx.de> (raw)
In-Reply-To: <alpine.DEB.2.20.1907230730580.19225@uplift.swm.pp.se>
Hi Mikael,
> On Jul 23, 2019, at 07:32, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>
> On Mon, 22 Jul 2019, Toke Høiland-Jørgensen wrote:
>
>> Anything derived from OpenWrt will also use FQ-CoDel on both WiFi and wired links. Not sure how common those are, though...
>
> I have OpenWrt derived devices that use hw acceleration
This is my min gripe with accelerators and off-load features, typically they side-step the linux kernel network stack and offer far less features than that stack (this is how they speed up things). IMHO these are crutches and at least up to 1Gbps links reasonable priced x86/x64 hardware can do routing with all bells and whistles (heck mvebu plattforms also come close).
> and they are not using FQ_CODEL. So OpenWrt in itself doesn't mean FQ_CODEL is used.
By default OpenWrt does not use hardware offloads (and IIRC it only supports hardware acceleration on mediatek SoCs) but defaults to fq_codel, so usage of OpenWrt should still be a strong indicator of fq_codel being used....
Best Regards
Sebastian
>
> --
> Mikael Abrahamsson email: swmike@swm.pp.se_______________________________________________
> Ecn-sane mailing list
> Ecn-sane@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/ecn-sane
next prev parent reply other threads:[~2019-07-23 5:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 14:14 Mikael Abrahamsson
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 [this message]
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=BAC8C466-E215-46AE-9D30-591A82055633@gmx.de \
--to=moeller0@gmx.de \
--cc=dave@taht.net \
--cc=ecn-sane@lists.bufferbloat.net \
--cc=jfoulkes@evenroute.com \
--cc=swmike@swm.pp.se \
--cc=toke@toke.dk \
--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