General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Fwd: Did *bufferbloat* cause the 2010 flashcrash?
Date: Fri, 7 Aug 2015 16:47:41 +0200	[thread overview]
Message-ID: <20150807144741.GB27438@sesse.net> (raw)
In-Reply-To: <87mvy3qi23.fsf@toke.dk>

On Fri, Aug 07, 2015 at 04:39:16PM +0200, Toke Høiland-Jørgensen wrote:
> 2. Bandwidth sharing between bittorrent and other protocols. Bittorrent
>    uses utp to try to be a scavenger that will back off and not use
>    bandwidth if other traffic needs it. fq_codel breaks this by
>    isolating flows and taking away the signal utp uses to back off.
>    Diffserv with a suitable scheduler (cake, for instance) can fix this
>    if the bittorrent client is configured correctly;

Well, I already pointed out that DSCP doesn't really work :-) For one, the
torrent client _isn't_ configured correctly. I have yet to actually see any
setting DSCP bits in practice, although I'm sure they exist (e.g. I heard
Dave was sending out patches).

>    or you could use
>    deep(er) packet inspection to try to figure out which traffic is
>    bittorent. But we don't have a shrinkwrap solution to this presently,
>    AFAIK.
> 
> I believe the cat video upload falls into category 2.

Yes, certainly.

In a sense, the only reasonable solution I can see to this problem is to have
two-level fq_codel (fair between senders, fair between flows for each
sender), but that simply doesn't exist. Also you'd need to reverse it for
downloads, and for someone in the middle, who knows what's actually up or
down.

/* Steinar */
-- 
Homepage: http://www.sesse.net/

  reply	other threads:[~2015-08-07 14:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4EDA85BE-CD86-4DA9-8ED5-78500E858F79@baylink.com>
2015-08-03  9:54 ` Dave Taht
2015-08-07 14:13   ` Livingood, Jason
2015-08-07 14:23     ` Steinar H. Gunderson
2015-08-07 14:28       ` Mikael Abrahamsson
2015-08-07 14:35         ` Toke Høiland-Jørgensen
2015-08-07 14:39           ` Toke Høiland-Jørgensen
2015-08-07 14:47             ` Steinar H. Gunderson [this message]
2015-08-07 14:43       ` Sebastian Moeller
2015-08-07 14:49         ` Steinar H. Gunderson
2015-08-07 14:59           ` Toke Høiland-Jørgensen
2015-08-07 15:09             ` 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=20150807144741.GB27438@sesse.net \
    --to=sgunderson@bigfoot.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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