From: Jim Gettys <jg@freedesktop.org>
To: Keith Winstein <keithw@mit.edu>
Cc: "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>
Subject: Re: [Codel] sprout
Date: Wed, 10 Jul 2013 16:46:09 -0400 [thread overview]
Message-ID: <CAGhGL2Cx7h_0Mx=q9=ZzSN99qAvu-vOtgkQZm6=b3H=B5RJ7ww@mail.gmail.com> (raw)
In-Reply-To: <CAMzhQmNDCXqWmFpo0gHU7tpxsH0VLS1HbKzkYUe=WvMNpva+xw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 817 bytes --]
On Wed, Jul 10, 2013 at 4:41 PM, Keith Winstein <keithw@mit.edu> wrote:
> On Wed, Jul 10, 2013 at 4:38 PM, Jim Gettys <jg@freedesktop.org> wrote:
>
>> Did you compare with fq_codel? None of us (Van included) advocate CoDel
>> by itself.
>>
>
> Hi Jim,
>
> In our evaluation there's only one flow over the queue (in each direction)
> -- the videoconference. So, yes.
>
> In the upcoming paper where we try and come up with the best end-to-end
> schemes for multiuser traffic, we compare against Cubic-over-sfqCoDel (
> http://www.pollere.net/Txtdocs/sfqcodel.cc).
>
Great.
I sure wish we could get together on *fq_codel variants. Kathy thinks that
there is no difference between sfq_codel and fq_codel, and Dave thinks
there is a difference.
Sigh....
- Jim
>
> Cheers,
> Keith
>
[-- Attachment #2: Type: text/html, Size: 2245 bytes --]
next prev parent reply other threads:[~2013-07-10 20:46 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 [this message]
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
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='CAGhGL2Cx7h_0Mx=q9=ZzSN99qAvu-vOtgkQZm6=b3H=B5RJ7ww@mail.gmail.com' \
--to=jg@freedesktop.org \
--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