From: Dave Taht <dave.taht@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Sebastian Moeller <moeller0@gmx.de>,
"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 03:57:29 -0700 [thread overview]
Message-ID: <CAA93jw5ptd-k6VcgEtiM-cJ5RgGewwbo8Dc8yC_SFfgsJhUyuQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1907230816070.19225@uplift.swm.pp.se>
On Mon, Jul 22, 2019 at 11:21 PM Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>
> On Tue, 23 Jul 2019, Sebastian Moeller wrote:
>
> > 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...
>
> On most HGW SOCs today the choice between HW offload on/off is 200
> megabit/s unidirectional with large packets, or very close to wirespeed.
>
> Anyhow, my statement is that of the users today on the Internet, their
> congestion point will not have FQ enabled, and this for 99% of users. I
> don't see any trend that this is on the verge of drastically increasing
> either.
>
> The trend I am seeing is that delay control is being deployed by means of
> RED, buffer size caps (basically implementing adaptive buffers to only
> provide 10ms buffering until tail drop), PIE/CODEL or similar.
I don't see a trend on "RED" - I see existing implementations.
Certainly most hardware offloads have fairly short buffer sizes. I
have been hoping for a pie implementation in non-cable-hw for years
now.
The title of this mail could just as well been, "have any hw offload
makers been paying the
slightest bit of attention to fixing bufferbloat with *any* aqm or fq
tech?" - with an answer of no.
On 10gige+ ethernet cards, 64 hw queues is the norm. That's fq.
There's some support for aqm
on some. I think the work on timerwheel paced stuff has high potential.
In the switch chip market we see big buffered switches and small
buffered ones, targetted at different markets. There's work in p4
that's promising on the switch front.
We've hit it out of the park on wifi, with atf and fq_codel. Very
visible "trend" there.
What happens in the offloaded word on small routers like the
edgerouter series is to do "qos" at a lower
than line rate, offloads are disabled and it's done in software.
The tit
> I'd be happy to be proven wrong.
>
> --
> Mikael Abrahamsson email: swmike@swm.pp.se
--
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740
prev parent reply other threads:[~2019-07-23 10: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
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 [this message]
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=CAA93jw5ptd-k6VcgEtiM-cJ5RgGewwbo8Dc8yC_SFfgsJhUyuQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=dave@taht.net \
--cc=ecn-sane@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
--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