From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] happy 4th!
Date: Thu, 4 Jul 2013 07:57:17 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.00.1307040751130.10894@uplift.swm.pp.se> (raw)
In-Reply-To: <CAA93jw7WPdxKwGGvQoSEfmDN3ey9j7+BNT5yohB6XUyCqbQRtQ@mail.gmail.com>
On Wed, 3 Jul 2013, Dave Taht wrote:
> Suggestions as to things to test and code to test them welcomed. In
I'm wondering a bit what the shallow buffering depth means to higher-RTT
connections. When I advocate bufferbloat solutions I usually get thrown in
my face that shallow buffering means around-the-world TCP-connections will
behave worse than with a lot of buffers (traditional truth being that you
need to be able to buffer RTT*2).
It would be very interesting to see what an added 100ms
(<http://stackoverflow.com/questions/614795/simulate-delayed-and-dropped-packets-on-linux>)
and some packet loss/PDV would result in. If it still works well, at least
it would mean that people concerned about this could go back to rest.
Also, would be interesting to see is Googles proposed QUIC interacts well
with the bufferbloat solutions. I imagine it will since it in itself
measures RTT and FQ_CODEL is all about controlling delay, so I imagine
QUIC will see a quite constant view of the world through FQ_CODEL.
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2013-07-04 5:57 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 [this message]
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
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.1307040751130.10894@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.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