From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Fwd: Did *bufferbloat* cause the 2010 flashcrash?
Date: Fri, 7 Aug 2015 16:23:37 +0200 [thread overview]
Message-ID: <20150807142337.GA22258@sesse.net> (raw)
In-Reply-To: <D1EA343B.10EA7E%jason_livingood@cable.comcast.com>
On Fri, Aug 07, 2015 at 02:13:20PM +0000, Livingood, Jason wrote:
> while customers were using BitTorrent (which led the company down a bad
> path to try to fix it but that¹s a long story).
But what _is_ a good path to fix the BitTorrent problem[1]? I still haven't
seen a real-life practical solution. LEDBAT is negated by fq_codel, DSCP
markings don't work (they get stripped, and usually were not even set to
begin with), switching to IP-level fairness makes life hard for the torrent
user (not that it seems to even exist in fq_codel; and two-level fq_codel
doesn't seem to exist either). DPI to single out torrent traffic? I think
we've sort of tried that. :-)
[1] For the purposes of the question, the “BitTorrent problem” is when you
and I are on the same network, and your 200+ BitTorrent upload sessions
makes it impossible for me to upload my single cat video to YouTube.
/* Steinar */
--
Homepage: http://www.sesse.net/
next prev parent reply other threads:[~2015-08-07 14:23 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 [this message]
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
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=20150807142337.GA22258@sesse.net \
--to=sgunderson@bigfoot.com \
--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