From: Mikael Abrahamsson <swmike@swm.pp.se>
To: dpreed@reed.com
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] happy 4th!
Date: Mon, 8 Jul 2013 02:24:25 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.00.1307080211340.10894@uplift.swm.pp.se> (raw)
In-Reply-To: <1373223178.486913695@apps.rackspace.com>
On Sun, 7 Jul 2013, dpreed@reed.com wrote:
> So when somebody "throws that in your face", just confidently use the
> words "Bullshit, show me evidence", and ignore the ignorant person who
Oh, the people that have told me this are definitely not ignorant. Quite
the contrary.
... and by the way, they're optimising for the case where a single TCP
flow from a 10GE connected host is traversing a 10G based backbone, and
they want this single TCP session to use every spare capacity the network
has to give. Not 90% of available capcity, but 100%.
This is the kind of people that have a lot of influence and causes core
routers to get designed with 600 ms of buffering (well, latest generation
ones are down to 50ms buffering). We're talking billion dollar investments
by hardware manufacturers. We're talking core routers of latest generation
that are still being put into production as we speak.
Calling them ignorant and trying to wave them off by that kind of
reasonsing isn't productive. Why not just implement the high RTT testing
part and prove that you're right instead of just saying you're right?
THe bufferbloat initiative is trying to change how things are done. Burden
of proof is here. When I participate in IETF TCP WG, they talk goodput.
They're not talking latency and interacting well with UDP based
interactive streams. They're optimising goodput. If we want buffers to be
lower, we need to convince people that this doesn't hugely affect goodput.
I have not so far seen tests with FQ_CODEL with a simulated 100ms extra
latency one-way (200ms RTT). They might be out there, but I have not seen
them. I encourage these tests to be done.
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2013-07-08 0:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 19:33 Dave Taht
2013-07-04 5:57 ` Mikael Abrahamsson
2013-07-04 13:51 ` Michael Richardson
2013-07-04 15:48 ` Mikael Abrahamsson
2013-07-07 18:52 ` dpreed
2013-07-08 0:24 ` Mikael Abrahamsson [this message]
2013-07-08 17:03 ` Toke Høiland-Jørgensen
2013-07-09 3:24 ` Dave Taht
2013-07-09 6:04 ` Mikael Abrahamsson
2013-07-09 6:32 ` Dave Taht
2013-07-09 7:30 ` [Cerowrt-devel] [Codel] " Andrew McGregor
2013-07-09 13:09 ` Eric Dumazet
2013-07-09 7:57 ` [Cerowrt-devel] " Toke Høiland-Jørgensen
2013-07-09 12:56 ` [Cerowrt-devel] [Codel] " Eric Dumazet
2013-07-09 13:13 ` Toke Høiland-Jørgensen
2013-07-09 13:23 ` Eric Dumazet
2013-07-09 13:25 ` Toke Høiland-Jørgensen
2013-07-09 13:36 ` Eric Dumazet
2013-07-09 13:45 ` Toke Høiland-Jørgensen
2013-07-09 13:49 ` Eric Dumazet
2013-07-09 13:53 ` Toke Høiland-Jørgensen
2013-07-09 14:07 ` Eric Dumazet
2013-07-08 20:50 ` [Cerowrt-devel] " dpreed
2013-07-08 21:04 ` Jim Gettys
2013-07-09 5:48 ` Mikael Abrahamsson
2013-07-09 5:58 ` dpreed
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.00.1307080211340.10894@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dpreed@reed.com \
/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