From: Hal Murray <hmurray@megapathdsl.net>
To: bloat@lists.bufferbloat.net
Cc: Hal Murray <hmurray@megapathdsl.net>
Subject: [Bloat] Really really big buffers
Date: Wed, 04 Mar 2015 13:17:58 -0800 [thread overview]
Message-ID: <20150304211758.33DDE406057@ip-64-139-1-69.sjc.megapath.net> (raw)
> Right now buffers routinely hold 10+ seconds worth of traffic (and Dave T
> showed the airline system buffering 10+ MINUTES of traffic)
I've seen similar unreasonable delays. I think that's a bug in some firmware.
My straw man is that something like a DSL link goes down and the router/modem
doesn't flush its queue. A while later, the box at the other end finishes
rebooting, the link comes back up, and the packet gets sent on its way.
--
These are my opinions. I hate spam.
next reply other threads:[~2015-03-04 21:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 21:17 Hal Murray [this message]
2015-03-04 21:49 ` Jonathan Morton
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=20150304211758.33DDE406057@ip-64-139-1-69.sjc.megapath.net \
--to=hmurray@megapathdsl.net \
--cc=bloat@lists.bufferbloat.net \
/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