General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
To: "Steinar H. Gunderson" <sgunderson@bigfoot.com>,
	"bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] came across an unexpected side-effect of bufferbloat
Date: Mon, 3 Aug 2015 14:11:33 +0000	[thread overview]
Message-ID: <AE7F97DB5FEE054088D82E836BD15BE94DC12BC1@xmb-aln-x05.cisco.com> (raw)
In-Reply-To: <20150803140054.GA5082@sesse.net>

It is even worse than that - On some really crappy low end devices, applications do not get a taste of the CPU if there is a packet to be sent. If there is always a packet to be sent, the SNMP daemon and/or some DOCSIS/DSL/FTTx tasks (and other application level tasks that need to interact with the control plane) don't run. Eventually something weird happens, like a memory leak or a dead-man timer and  the box reboots. Clearly, this is sub-optimal. 

Fortunately, Darwinian pressures have made this type of device less prevalent in the marketplace. You can still run into some really poor CPE in the wild, though.


Bill VerSteeg

-----Original Message-----
From: bloat-bounces@lists.bufferbloat.net [mailto:bloat-bounces@lists.bufferbloat.net] On Behalf Of Steinar H. Gunderson
Sent: Monday, August 03, 2015 10:01 AM
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] came across an unexpected side-effect of bufferbloat

On Mon, Aug 03, 2015 at 11:53:40PM +1000, jb wrote:
> While researching a little I came across a message on the Amazon 
> support forums that said after 3 hours of uploading to Amazon, their 
> cable modem would crash and reboot. The reason was that the SNMP the 
> cable modem needed to stay healthy was timing out (due to the 
> excessive latency induced by the continuous uploading). The author didn't know it was bufferbloat, of course.

FWIW, you don't need bufferbloat for this to fail. A classic thing with switches (typically underbuffered rather than overbuffered!) is that when you run the links full, the OSPF packets get dropped and eventually your link flaps because the other side thinks you're down.

This is one of the reasons why most L3 switches (well, anything that's advanced enough to do OSPF or the likes in the first place :-) ) have QoS at
all: You need to protect your administrative traffic.

/* Steinar */
--
Homepage: http://www.sesse.net/
_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/bloat

  reply	other threads:[~2015-08-03 14:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 13:53 jb
2015-08-03 14:00 ` Steinar H. Gunderson
2015-08-03 14:11   ` Bill Ver Steeg (versteb) [this message]
2015-08-03 14:55   ` 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=AE7F97DB5FEE054088D82E836BD15BE94DC12BC1@xmb-aln-x05.cisco.com \
    --to=versteb@cisco.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=sgunderson@bigfoot.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