From: Dave Taht <dave.taht@gmail.com>
To: Keith Winstein <keithw@mit.edu>
Cc: codel@lists.bufferbloat.net
Subject: Re: [Codel] sprout
Date: Wed, 10 Jul 2013 13:40:59 -0700 [thread overview]
Message-ID: <CAA93jw4LTpYjZsG9cypXNguh6+NUYqG0oOGON=BU8B7FDzbTmQ@mail.gmail.com> (raw)
In-Reply-To: <CAMzhQmOZ=O6LkXh4GtOJok5PuspPEK2fFgg0pNqiAhiosk2pAA@mail.gmail.com>
On Wed, Jul 10, 2013 at 1:19 PM, Keith Winstein <keithw@mit.edu> wrote:
> Thank, Dave.
>
> We have a Web site with more info, a talk, and source code
> (http://alfalfa.mit.edu) if anybody is interested.
Good Talk! Nice way to spend lunch. Boy you talk fast.
The simple expedient of inverting the delay scale against the
bandwidth scale had never occurred to me on the graph, up and to the
right helps!
How did you dynamically stretch out the graphs like that in the preso?
I'd like very much to be able to zoom into those levels of detail and
out again.
Lastly,
what was sprout and sprout-ewma over codel? (rather than vs codel)
> Something that may interest folks here is that we compared
> Sprout-over-unlimited-buffer with TCP-Cubic-over-CoDel on these
> cellular-type links. That is, a scenario where the network operators
> implemented CoDel inside the LTE/UMTS/1xEV-DO base station (for the
> downlink) and the phone manufacturers implemented CoDel inside the
> "baseband" chip for the uplink.
of course I'm always after people to attempt fq_codel in cases like this...
or fq + X, whatever X is....
>
> Bottom line results is that for the case where a cellular user can control
> all their own flows, it's roughly a wash. To a first approximation, you can
> fix bufferbloat on a cellular network *either* by putting CoDel inside the
> base station and baseband chip (and otherwise running the same endpoint
> TCP), *or* by changing the endpoints but leaving the base station and
> baseband chip unmodified.
>
> Obviously we benefit dramatically from the per-user queues of the cellular
> network. By contrast, in a typical house with a bufferbloated cable modem
> where one user can cause big delays for everybody else, you can't fix
> bufferbloat by fixing just one endpoint. We will have some results soon on
> whether you can fix it by fixing all the endpoints (but still leaving the
> "bloated" gateway intact).
>
> Cheers,
> Keith
>
> On Wed, Jul 10, 2013 at 3:30 PM, Dave Taht <dave.taht@gmail.com> wrote:
>>
>> I haven't been paying a lot of attention to rmcat and webrtc until
>> recently, although I'd had a nice discussion with keith on it a while
>> back..
>>
>> this particular thread sums up some interesting issues on that front.
>>
>> http://www.ietf.org/mail-archive/web/rmcat/current/msg00390.html
>>
>> --
>> Dave Täht
>>
>> Fixing bufferbloat with cerowrt:
>> http://www.teklibre.com/cerowrt/subscribe.html
>
>
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
prev parent reply other threads:[~2013-07-10 20:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 19:30 Dave Taht
2013-07-10 20:19 ` Keith Winstein
2013-07-10 20:38 ` Jim Gettys
2013-07-10 20:41 ` Keith Winstein
2013-07-10 20:46 ` Jim Gettys
2013-07-10 21:42 ` Dave Taht
2013-07-10 22:10 ` Kathleen Nichols
2013-07-10 22:44 ` Dave Taht
2013-07-10 23:07 ` Eric Dumazet
2013-07-11 15:45 ` Kathleen Nichols
2013-07-11 16:22 ` Eric Dumazet
2013-07-11 16:54 ` Kathleen Nichols
2013-07-11 17:17 ` Dave Taht
2013-07-10 20:40 ` Dave Taht [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/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw4LTpYjZsG9cypXNguh6+NUYqG0oOGON=BU8B7FDzbTmQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=codel@lists.bufferbloat.net \
--cc=keithw@mit.edu \
/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