General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: davecb@spamcop.net
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] ipspace.net: "QUEUING MECHANISMS IN MODERN SWITCHES", > (Jonathan Morton)
Date: Thu, 29 May 2014 17:09:55 +0300	[thread overview]
Message-ID: <CAJq5cE2f-jBYaeqQx_8EswGOgiM_CFim_uX0u9RqynL4=jwxNg@mail.gmail.com> (raw)
In-Reply-To: <53861CEB.8060003@rogers.com>

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

On 28 May 2014 20:31, "David Collier-Brown" <davec-b@rogers.com> wrote:
>
> On 05/28/2014 11:33 AM, Jonathan Morton <chromatix99@gmail.com> wrote
> > It's a mathematical truth for any topology that you can reduce to a
black box with one or more inputs and one output, which you call a "queue"
and which *does
> not discard* packets.  Non-discarding queues don't exist in the real
> world, of course.
> >
> > The intuitive proof is that every time you promote a packet to be
transmitted earlier, you must demote one to be transmitted later.  A
non-FIFO queue tends to increase the maximum delay and decrease the minimum
delay, but the average delay will remain constant.
>
> A niggle: people working in queuing theory* make the simplifying
> assumption that queues don't drop. When describing the real world, they
> talk of "defections", the scenario where a human arrives at the tail of
> the queue and "defects", either to another queue or to the exit door of
> the store!

I think my description of the black box is still valid: a "defection" must
imply a second output from the box, otherwise it will appear as either a
reordering (preserving the property) or a discard.

- Jonathan Morton

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

  parent reply	other threads:[~2014-05-29 14:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.45496.1401291224.1815.bloat@lists.bufferbloat.net>
2014-05-28 17:29 ` David Collier-Brown
2014-05-29  7:28   ` Neil Davies
2014-05-29 14:09   ` Jonathan Morton [this message]
2014-05-29 15:36     ` David 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='CAJq5cE2f-jBYaeqQx_8EswGOgiM_CFim_uX0u9RqynL4=jwxNg@mail.gmail.com' \
    --to=chromatix99@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=davecb@spamcop.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