General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Hal Murray <hmurray@megapathdsl.net>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Really really big buffers
Date: Wed, 4 Mar 2015 23:49:38 +0200	[thread overview]
Message-ID: <CAJq5cE1DtHKGu7LdMvXe+cKCBoDZLvBe1FLdwH1ZEOSPKKkqNA@mail.gmail.com> (raw)
In-Reply-To: <20150304211758.33DDE406057@ip-64-139-1-69.sjc.megapath.net>

[-- Attachment #1: Type: text/plain, Size: 796 bytes --]

No, I don't think that's what's happening.

The in-flight one, which is the most egregious example, shows the queue
gradually draining at the end of the flight, when all the passengers have
been told to turn their lap warmers and fondleslabs off.

I personally have seen 45 seconds buffering delays with continuous delivery
at half a megabit or so, resulting from a market segmentation shaper in a
3G network using a big, drop tail queue. In fact, I could probably
reproduce that effect using the hardware in my hands right now.

The FireBrick, a custom firmware router made by A&A to go with their
services, is reportedly capable of rebooting without losing a packet. But
it does so by completing the reboot extremely quickly - a fraction of a
second. (It doesn't run Linux.)

- Jonathan Morton

[-- Attachment #2: Type: text/html, Size: 909 bytes --]

      reply	other threads:[~2015-03-04 21:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04 21:17 Hal Murray
2015-03-04 21:49 ` Jonathan Morton [this message]

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=CAJq5cE1DtHKGu7LdMvXe+cKCBoDZLvBe1FLdwH1ZEOSPKKkqNA@mail.gmail.com \
    --to=chromatix99@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=hmurray@megapathdsl.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