General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Jan Ceuleers <jan.ceuleers@gmail.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] [Cerowrt-devel] beating the drum for BQL
Date: Thu, 23 Aug 2018 23:22:07 +0900	[thread overview]
Message-ID: <360212B1-8411-4ED0-877A-92E59070F518@gmx.de> (raw)
In-Reply-To: <66e2374b-f998-b132-410e-46c9089bb06b@gmail.com>

Hi Jan,


> On Aug 23, 2018, at 22:57, Jan Ceuleers <jan.ceuleers@gmail.com> wrote:
> 
> On 23/08/18 15:06, Sebastian Moeller wrote:
>> 	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...
> 
> Not realistic, and also not environmentally friendly.

	I unhappily agree with the first (market forces being what they are); I claim the second is untrue, since I stipulated packet accelerators as a way save energy and alllowing a competent main CPU to idle in low power mode, but pack the punch if needed. That sounds more environmentally sane than the current model in which you have to replace the incompetent router by a more competent one later... (and my issue is not that a router needs to last forever, but the e.g. an ISP supplied router should be able to handle at least the sold plan's bandwidth with its main CPU...)

> 
> Doing packet forwarding in hardware is much more energy efficient, for
> example. So not only is the hardware cheaper, it doesn't generate as
> much heat, is cheaper to run, etc.

	Sure doing less/ a half asses job is less costly than doing it right, but in the extreme not doing the job at all saves even more energy ;). And I am not sure we are barking up the right tree here, it is not that all home CPE are rigorously optimized for low power and energy saving... my gut feeling is that the only optimizing principle is cost for the manufacturer/OEM and that causes underpowered CPU that are packet-accerlerated"-doped to appear to be able to do their job. I might be wrong though, as I have ISP internal numbers on this issue.

Best Regards
	Sebastian

> 
> Jan
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat


  reply	other threads:[~2018-08-23 14:22 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   ` [Bloat] [Cerowrt-devel] " Sebastian Moeller
2018-08-23 13:57     ` Jan Ceuleers
2018-08-23 14:22       ` Sebastian Moeller [this message]
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=360212B1-8411-4ED0-877A-92E59070F518@gmx.de \
    --to=moeller0@gmx.de \
    --cc=bloat@lists.bufferbloat.net \
    --cc=jan.ceuleers@gmail.com \
    /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