General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: David Collier-Brown <davecb.42@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>, tomh@tomh.org
Cc: bloat@lists.bufferbloat.net, davecb@spamcop.net
Subject: Re: [Bloat] Sidebar to "How about a topical LWN article on demonstrating the real-world goodness of CAKE?"
Date: Mon, 10 Aug 2020 10:16:38 -0400	[thread overview]
Message-ID: <46f7fff8-a441-6aaf-7ae7-77ee8273b5f7@rogers.com> (raw)
In-Reply-To: <fdpzkz.qetg01.2wxsbn-qmf@smtp.gmail.com>

On 2020-08-09 5:35 p.m., Jonathan Morton wrote:

> Most CPE devices these days rely on hardware accelerated packet forwarding to achieve their published specs.  That's all about taking packets in one side and pushing them out the other as quickly as possible, with only minimal support from the CPU (likely, new connections get a NAT/firewall lookup, that's all).  It has the advantages of speed and power efficiency, but unfortunately it is also incompatible with our debloating efforts.  So debloated CPE will tend to run hotter and with lower peak throughput, which may be noticeable to cable and fibre users; VDSL (FTTC) users might have service of 80Mbps or less where this effect is less likely to matter.
I have an interest in the next step up from mass-market routers, and 
this description made my ears prick up.

At work we have a decent network, carefully designed about 15 years ago 
to get work from Akamai, distribute it over mostly-in-the-same-DC 
service providers, then return it to the end-user customer. The IT folks 
don't know how it works, but are confident that it does (;-))

The nets we use for WFH are a little newer, but we had no idea if we 
were going to be able to work from home or hold conference calls with 
400-odd people. So we had to send everyone home on a Monday to try the 
experiment. Fortunately it worked.

That makes me curious about the customer-premises equipment we and 
others have, and to what degree it can be de-bloated. I know the 
datacenter vendors were being resistant when the problem was first 
solved, but I've not heard anything positive to date.  Cisco makes 
vaguely hand-wavey statements about DOCSIS 3.1 and PIE, but doesn't seem 
to answer customer questions,

What do we know about large-home and small-office devices these days?

--dave

-- 
David Collier-Brown,         | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net           |                      -- Mark Twain


  parent reply	other threads:[~2020-08-10 14:16 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-09 18:27 [Bloat] How about a topical LWN article on demonstrating the real-world goodness of CAKE? David Collier-Brown
2020-08-09 19:18 ` Tom Henderson
2020-08-09 21:35   ` Jonathan Morton
2020-08-10 12:57     ` David Collier-Brown
2020-08-10 14:00       ` Daniel Sterling
2020-08-10 15:08         ` Tom Henderson
2020-08-10 15:34           ` Sebastian Moeller
2020-08-10 15:57             ` Jonathan Morton
2020-08-10 16:04               ` Tom Henderson
2020-08-11 12:43         ` Daniel Sterling
2020-08-11 13:57           ` Kenneth Porter
     [not found]           ` <D8B6D86243E4539BBA58E32C@172.27.17.193>
2020-08-11 14:09             ` Daniel Sterling
2020-08-11 14:11               ` Daniel Sterling
2020-08-11 16:19                 ` Kenneth Porter
2020-08-10 17:58       ` Jonathan Foulkes
2020-08-10 19:13         ` Carlos R. Pasqualini
2020-08-10 20:28         ` Dave Collier-Brown
2020-08-11 12:41           ` Michael Yartys
2020-08-10 14:16     ` David Collier-Brown [this message]
2020-08-11 15:48     ` Simon Barber
2020-09-05 18:52 ` Dave Taht
2020-09-05 20:35   ` Dave Collier-Brown
2020-09-07  9:23     ` Toke Høiland-Jørgensen
2020-09-07 11:33       ` Dave Collier-Brown
2020-09-07 17:20         ` David Collier-Brown
2020-09-08 15:43           ` Dave Taht
2020-09-08 16:48             ` Matt Mathis
2020-09-08 17:09               ` Jonathan Morton
2020-09-10 15:08                 ` Anthony Minessale II
2020-09-10 16:52                   ` Dave Collier-Brown

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=46f7fff8-a441-6aaf-7ae7-77ee8273b5f7@rogers.com \
    --to=davecb.42@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=davecb@spamcop.net \
    --cc=tomh@tomh.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