From: Sebastian Moeller <moeller0@gmx.de>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: "Dave Täht" <dave.taht@gmail.com>,
cerowrt-devel@lists.bufferbloat.net,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Cerowrt-devel] beating the drum for BQL
Date: Thu, 23 Aug 2018 22:06:46 +0900 [thread overview]
Message-ID: <F508D2DC-474B-4E90-BDEC-97874A4E9194@gmx.de> (raw)
In-Reply-To: <alpine.DEB.2.20.1808230746320.19688@uplift.swm.pp.se>
Hi Mikael,
> On Aug 23, 2018, at 14:47, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>
> On Wed, 22 Aug 2018, Dave Taht wrote:
>
>> I/we really should have beat the bql drum harder over the last 6 years. It's the basic start to all the debloating.
>
> It only helps with kernel based forwarding. A lot of devices don't even use this, especially as speeds go up. They use packet accelerators so the kernel never sees the packets after initial flow setup.
>
> So you need to get the people developing that silicon to get with the program.
Or we could convince customers to stop buying toy router's that only work under a severely limited set of circumstances and opt for devices that pack enough CPU-punch to be actually adequate for modern internet speed tiers, no? Now if the packet accelerator is jus there to help save energy for typical cases but the CPU is powerful enough to handle a modern line with all the bells and whistles customers except, then I am all for it, but if the packet accelerator is just there to paper over an anemic CPU...
Best Regards
Sebastian
P.S.: I ignore issues of cost for ISP supplied CPE devices here since a) most ISPs I know actually charge rent for these devices now b) should have enough volume to drive down prices even for devices that are sufficiently fast for at least the 300 - 500 Mbps class of combined up- and download....
>
> --
> Mikael Abrahamsson email: swmike@swm.pp.se
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2018-08-23 13:06 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 0:49 [Bloat] " Dave Taht
2018-08-23 5:47 ` Mikael Abrahamsson
2018-08-23 13:06 ` Sebastian Moeller [this message]
2018-08-23 13:57 ` [Bloat] [Cerowrt-devel] " Jan Ceuleers
2018-08-23 14:22 ` Sebastian Moeller
2018-08-23 15:32 ` Mikael Abrahamsson
2018-08-23 17:14 ` Rosen Penev
2018-08-23 17:50 ` Mikael Abrahamsson
2018-08-23 18:21 ` Dave Taht
2018-08-23 20:15 ` Dave Taht
2018-08-24 7:00 ` Mikael Abrahamsson
2018-08-24 8:06 ` Dave Taht
2018-08-24 11:22 ` Toke Høiland-Jørgensen
2018-08-24 11:46 ` Jan Ceuleers
2018-08-24 13:43 ` Jan Ceuleers
2018-08-24 13:44 ` Mikael Abrahamsson
2018-08-24 13:56 ` Jan Ceuleers
2018-08-24 13:36 ` Mikael Abrahamsson
2018-08-24 7:05 ` Mikael Abrahamsson
2018-08-24 11:24 ` Toke Høiland-Jørgensen
2018-08-23 21:01 ` Toke Høiland-Jørgensen
2018-08-24 14:44 ` Dave Taht
2018-08-24 17:58 ` Toke Høiland-Jørgensen
2018-08-23 23:35 ` Sebastian Moeller
2018-08-24 1:08 ` David Collier-Brown
2018-08-24 6:16 ` Jan Ceuleers
2018-08-24 11:27 ` Toke Høiland-Jørgensen
2018-08-24 12:46 ` Pedro Tumusok
2018-08-24 13:09 ` Michael Richardson
2018-08-24 13:37 ` Mikael Abrahamsson
2018-08-24 13:44 ` Toke Høiland-Jørgensen
2018-08-26 4:29 ` [Bloat] Marvell 385 Dave Taht
2018-08-26 4:32 ` Jonathan Morton
2018-08-26 16:28 ` Rosen Penev
2018-08-26 18:44 ` Mikael Abrahamsson
2018-08-26 20:53 ` Dave Taht
2018-08-26 20:58 ` Rosen Penev
2018-08-26 21:08 ` Dave Taht
2018-08-27 0:55 ` Rosen Penev
2018-08-27 1:21 ` Dave Taht
2018-08-27 1:33 ` Rosen Penev
2018-08-27 1:45 ` Dave Taht
2018-08-27 1:53 ` Rosen Penev
2018-08-27 11:33 ` Mikael Abrahamsson
2018-08-23 8:26 ` [Bloat] beating the drum for BQL Pete Heist
2018-08-23 10:51 ` Mikael Abrahamsson
2018-08-23 11:38 ` Pete Heist
2018-08-24 17:13 ` Pete Heist
2018-08-24 17:30 ` Dave Taht
2018-08-24 18:43 ` 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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F508D2DC-474B-4E90-BDEC-97874A4E9194@gmx.de \
--to=moeller0@gmx.de \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=swmike@swm.pp.se \
/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