From: Sebastian Moeller <moeller0@gmx.de>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: "Dave Täht" <dave.taht@gmail.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 08:13:24 +0200 [thread overview]
Message-ID: <7C7CE2C6-DCB2-4AEB-BB6B-44A707180D7A@gmx.de> (raw)
In-Reply-To: <alpine.DEB.2.20.1907230732420.19225@uplift.swm.pp.se>
> On Jul 23, 2019, at 07:34, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>
> On Mon, 22 Jul 2019, Dave Taht wrote:
>
>> Hmm? Nearly everything derived from openwrt commercially has it. More generally, debian linux derived Google wifi, chromebooks, eero have publically disclosed their usage.
>
> For CPU based forwarding platforms, perhaps (and these are not the common ones). But one of the few OpenWrt hw acceleration platforms (MT7621) then FQ is not done on the hw accelerated flows afaik.
>
> HW acceleration typically means FQ goes out the window.
That, and most other features the linux network stack offers (it is easier ot be fast if you do less ;) ) I believe users need to actively enable HW offloading, so shpould be in control whether they want to trade in a ship-load of features for alloing their router to punch well above its weight...
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 6:13 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
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 [this message]
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=7C7CE2C6-DCB2-4AEB-BB6B-44A707180D7A@gmx.de \
--to=moeller0@gmx.de \
--cc=dave.taht@gmail.com \
--cc=dave@taht.net \
--cc=ecn-sane@lists.bufferbloat.net \
--cc=swmike@swm.pp.se \
--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