General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dave Taht <dave.taht@gmail.com>
Cc: Sebastian Moeller <moeller0@gmx.de>,
	 bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] fixing bufferbloat in 2017
Date: Wed, 23 Nov 2016 21:39:21 +0100	[thread overview]
Message-ID: <878tsarkw6.fsf@toke.dk> (raw)
In-Reply-To: <CAA93jw6PF+NNOP0vxP70iMbdUMKE4pbeCgmw4GKep=0UWYcw5A@mail.gmail.com> (Dave Taht's message of "Wed, 23 Nov 2016 10:24:16 -0800")

Dave Taht <dave.taht@gmail.com> writes:

> On Wed, Nov 23, 2016 at 10:18 AM, Sebastian Moeller <moeller0@gmx.de> wrote:
>>
>>> On Nov 23, 2016, at 19:09, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>>>
>>> On Wed, 23 Nov 2016, David Lang wrote:
>>>
>>>> Deploy what we already know to work on the real edge devices and things get vastly simpler.
>>
>>         One problem will be that the actual edge devices are often ISP
>>         supplied and hence extremely cost sensitive; combined with increasing
>>         bandwidth in many ISP offerings, having CPEs that can perform ingress
>>         shaping at “modern” rates looks challenging if the same CPEs also need
>>         to be very cheap. Egress shaping is a different kettle of fish though
>>         and for most asymmetric plans the CPE either should have enough punch
>>         or might be amendable to a BQL-like solution that could e actually
>>         relatively computationally cheap. But for that to happen we would need
>>         to convince ISPs and/or CPE chipset manufacturer (or better those
>>         engineers that create the drivers for the SDKs).
>
> One benefit of the fq_codel on wifi work is that for homes that are
> primarily wifi, you no longer need inbound rate shaping to work, you
> can do it on the wifi naturally.
>
> A long term plan might be to try to develop code that could be used at
> the ISP, a transparent bridge that would take over customer rate
> shaping and queue management. Hardware "good enough" to do this,
> ranging from high end xeons to the next generation NXP products, to
> mellonox's bluefield thing, is arriving, and I anticipate being able
> to effectively fq and shape 1000s of customers with gear that costs
> less than 10k - maybe not with linux, but with vpp and/or dpdk.

I happen to know of at least one company that offers this kind of middle
box and also ships CoDel and BLUE (I think it was). Those are DPI boxes,
though (*shudder*) -- and I think the price tag is quite a bit more than
$10k... :/

-Toke

  reply	other threads:[~2016-11-23 20:39 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-22 15:32 Dave Taht
2016-11-22 16:19 ` Jan Ceuleers
2016-11-22 16:25   ` Dave Taht
2016-11-22 16:38     ` Jim Gettys
2016-11-23  8:28     ` Mikael Abrahamsson
2016-11-23 11:04       ` Jonathan Morton
2016-11-23 11:59       ` Kelvin Edmison
2016-11-23 13:31         ` Pedro Tumusok
2016-11-23 14:05           ` Mário Sérgio Fujikawa Ferreira
2016-11-23 17:20           ` Mikael Abrahamsson
2016-11-23 17:27             ` Benjamin Cronce
2016-11-23 17:31               ` Mikael Abrahamsson
2016-11-23 17:40                 ` Sebastian Moeller
2016-11-23 17:50                 ` Noah Causin
2016-11-23 17:56                   ` David Lang
2016-11-23 18:05                     ` Benjamin Cronce
2016-11-23 18:38                       ` David Lang
2016-11-23 19:29                         ` Benjamin Cronce
2016-11-23 19:42                           ` David Lang
2016-11-23 20:20                             ` Dave Taht
2016-11-23 17:54                 ` David Lang
2016-11-23 18:09                   ` Mikael Abrahamsson
2016-11-23 18:18                     ` Sebastian Moeller
2016-11-23 18:24                       ` Dave Taht
2016-11-23 20:39                         ` Toke Høiland-Jørgensen [this message]
2016-11-23 19:13                       ` David Lang
2016-11-23 18:17                   ` Dave Taht
2016-11-23 15:32 ` Pedretti Fabio
2016-11-23 19:29   ` Stephen Hemminger
2016-11-23 19:22 ` Dave Taht
     [not found] <mailman.447.1479909940.3555.bloat@lists.bufferbloat.net>
2016-11-23 18:16 ` Rich Brown
2016-11-23 18:46   ` David Lang
2016-11-23 18:58     ` Jonathan Morton
2016-11-23 19:15       ` David Lang
2016-11-23 20:37       ` Toke Høiland-Jørgensen
     [not found] <mailman.454.1479929363.3555.bloat@lists.bufferbloat.net>
2016-11-26 15:33 ` [Bloat] Fixing " Rich Brown
2016-11-27  1:53   ` Aaron Wood
2016-11-27  6:10     ` Mikael Abrahamsson
2016-11-27 21:24   ` Dave Taht
2016-11-28  2:11     ` Kathleen Nichols
2016-11-28  2:16       ` Jim Gettys
2016-11-28  6:00         ` Jan Ceuleers
2016-11-28 12:48           ` David Collier-Brown
2016-11-28 15:12             ` Dave Taht
2016-11-28 15:23               ` Wesley Eddy
2016-11-28 15:35                 ` Dave Taht
2016-11-28 16:58                   ` Stephen Hemminger
2016-11-28 17:07                     ` Dave Taht
2016-11-28 19:02                       ` Jonathan Morton
2016-11-28 17:52                     ` Kathleen Nichols
2016-11-28 15:14             ` Pedro Tumusok
2016-11-28 15:23               ` Dave Taht
2016-11-28 15:10           ` Dave Taht
2016-11-28  2:47       ` David Lang

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=878tsarkw6.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=moeller0@gmx.de \
    /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