From: Jonathan Morton <chromatix99@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Mikael Abrahamsson <swmike@swm.pp.se>,
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 02:06:07 -0400 [thread overview]
Message-ID: <4E959AE1-9616-4F30-B93B-76BE5BA3D278@gmail.com> (raw)
In-Reply-To: <BAC8C466-E215-46AE-9D30-591A82055633@gmx.de>
> On 23 Jul, 2019, at 1:57 am, Sebastian Moeller <moeller0@gmx.de> wrote:
>
> 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).
May I introduce you to https://tools.ietf.org/html/draft-morton-tsvwg-cheap-nasty-queueing-00 ? I'm also in the process of expanding the LFQ draft. I think they show that HW acceleration *shouldn't* mean just dumb FIFOs.
> IMHO these are crutches and at least up to 1Gbps links reasonable priced x86/x64 hardware can do routing with all bells and whistles
I'd actually be rather interested to see what a Raspberry Pi 4 with a GigE USB3 dongle tacked on can cope with, now that it has native GigE through a direct PHY connection instead of via a USB2 bottleneck. That would be in the rough price range of a basic wifi router, and I've already got a Pi 2B running as an SCE endpoint.
Any idea which shops I should look in while I'm in Montreal?
- Jonathan Morton
next prev parent reply other threads:[~2019-07-23 6:06 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 [this message]
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=4E959AE1-9616-4F30-B93B-76BE5BA3D278@gmail.com \
--to=chromatix99@gmail.com \
--cc=dave@taht.net \
--cc=ecn-sane@lists.bufferbloat.net \
--cc=jfoulkes@evenroute.com \
--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