General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: richard <richard@pacdat.net>
To: Juliusz Chroboczek <Juliusz.Chroboczek@pps.jussieu.fr>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] First draft of complete "Bufferbloat And You" enclosed.
Date: Tue, 08 Feb 2011 11:52:30 -0800	[thread overview]
Message-ID: <1297194750.11917.3.camel@amd.pacdat.net> (raw)
In-Reply-To: <7ilj1qcnxs.fsf@lanthane.pps.jussieu.fr>

On Tue, 2011-02-08 at 20:43 +0100, Juliusz Chroboczek wrote:
> > If too many cars try to use the road at once, bad things happen.  One
> > of those bad things is cars running off the road and crashing. The
> > Internet analog of this is called 'packet loss'. We want to hold it to
> > a minimum.
> 
> I object to that, since it compares packet loss to a catastrophic
> failure.  (I would personally argue against a car analogy in the first
> place, but that's just stylistic preference.)
> 
This bothers me too. You almost have to inject a "MacGuffin" in the form
of a magic transporter at the entrance to all parking lots such that any
car that does not fit gets magically transported back to its origination
to try again - packet loss and retry - not catastrophic but very much a
penalty.

> > Suppose your rule for when a car gets to leave the parking lot is the
> > simplest possible: it fills up until it overflows, then cars are let
> > out the downstream side as fast as they can go.
> 
> I'm not sure what kind of buffer you're trying to illustrate.  That's
> certainly not how I understand tail-drop buffers.
> 
> Finally, I'd argue that you're being too harsh on QoS techniques.
> 
> --Juliusz
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
-- 
Richard C. Pitt                 Pacific Data Capture
rcpitt@pacdat.net               604-644-9265
http://digital-rag.com          www.pacdat.net
PGP Fingerprint: FCEF 167D 151B 64C4 3333  57F0 4F18 AF98 9F59 DD73


      reply	other threads:[~2011-02-08 19:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-05 13:23 Eric Raymond
2011-02-05 13:42 ` Jim Gettys
2011-02-05 15:12   ` Dave Täht
2011-02-05 15:46 ` Dave Täht
2011-02-06 13:37   ` Eric Raymond
2011-02-05 17:56 ` richard
2011-02-05 19:48 ` richard
2011-02-05 22:12   ` Dave Täht
2011-02-06  1:29     ` richard
2011-02-06  2:35       ` Dave Täht
2011-02-06  2:50         ` richard
2011-02-08 15:17 ` Justin McCann
2011-02-08 18:18   ` Eric Raymond
2011-02-08 18:31     ` richard
2011-02-08 18:50     ` Bill Sommerfeld
2011-02-09 15:50       ` Eric Raymond
2011-02-08 20:10     ` Sean Conner
2011-02-09  4:24     ` Justin McCann
2011-02-10 14:55       ` Jim Gettys
2011-02-10 17:50         ` Dave Täht
2011-02-08 19:43 ` Juliusz Chroboczek
2011-02-08 19:52   ` richard [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=1297194750.11917.3.camel@amd.pacdat.net \
    --to=richard@pacdat.net \
    --cc=Juliusz.Chroboczek@pps.jussieu.fr \
    --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