CoDel AQM discussions
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: codel@lists.bufferbloat.net
Subject: Re: [Codel] fq_codel : interval servo
Date: Sun, 2 Sep 2012 17:18:19 -0700	[thread overview]
Message-ID: <CAA93jw4igKGLWCd5SFuuRGhSef4MQhJRjGSrBUmbmQg4J_U3Jg@mail.gmail.com> (raw)
In-Reply-To: <1346628216.2563.70.camel@edumazet-glaptop>

On Sun, Sep 2, 2012 at 4:23 PM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
> On Sun, 2012-09-02 at 11:08 -0700, Dave Taht wrote:
>> On Sat, Sep 1, 2012 at 5:53 AM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
>> > On Fri, 2012-08-31 at 09:59 -0700, Dave Taht wrote:
>> >
>> >> I realize that 10GigE and datacenter host based work is sexy and fun,
>> >> but getting stuff that runs well in today's 1-20Mbit environments is
>> >> my own priority, going up to 100Mbit, with something that can be
>> >> embedded in a SoC. The latest generation of SoCs all do QoS in
>> >> hardware... badly.
>> >
>> > Maybe 'datacenter' word was badly chosen and you obviously jumped on it,
>> > because it meant different things for you.
>>
>> I am hypersensitive about optimizing for sub-ms problems when there are
>> huge multi-second problems like in cable, wifi, and cellular. Recent paper:
>>
>> http://conferences.sigcomm.org/sigcomm/2012/paper/cellnet/p1.pdf
>
> Yes. Take a deep breath, please.
>
> In France, we use to say : "Rome ne s'est pas faite en un jour"
>
> It means you wont solve all your problems at once.

Comforting.

> Step by step we improve things, and we discover new issues or
> possibilities.
>
> So denying one particular improvement is not good because it doesnt
> solve the 'Bufferbloat in the known Universe' is not very helpful.

I didn't say that. I LOVE that you and lots of people are fiddling
with various ideas around the core
codel concepts, and clearly said I think it's neat...

My larger question, poorly put, was:

what would applying ideas to codel based on measured tcp srrt,
do in the larger known universe as (for example) outlined by the data in that
paper, along with different tcps of any flavor at any rtt?

your original thought was to limit it to the local lan somehow.


-- 
Dave Täht
http://www.bufferbloat.net/projects/cerowrt/wiki - "3.3.8-17 is out
with fq_codel!"

  reply	other threads:[~2012-09-03  0:18 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-31  6:55 Eric Dumazet
2012-08-31 13:41 ` Jim Gettys
2012-08-31 13:50 ` [Codel] [RFC] fq_codel : interval servo on hosts Eric Dumazet
2012-08-31 13:57   ` [Codel] [RFC v2] " Eric Dumazet
2012-09-01  1:37     ` Yuchung Cheng
2012-09-01 12:51       ` Eric Dumazet
2012-09-04 15:10         ` Nandita Dukkipati
2012-09-04 15:25           ` Jonathan Morton
2012-09-04 15:39             ` Eric Dumazet
2012-09-04 15:34           ` Eric Dumazet
2012-09-04 16:40             ` Dave Taht
2012-09-04 16:54               ` Eric Dumazet
2012-09-04 16:57               ` Eric Dumazet
2012-08-31 15:53 ` [Codel] fq_codel : interval servo Rick Jones
2012-08-31 16:23   ` Eric Dumazet
2012-08-31 16:59     ` Dave Taht
2012-09-01 12:53       ` Eric Dumazet
2012-09-02 18:08         ` Dave Taht
2012-09-02 18:17           ` Dave Taht
2012-09-02 23:28             ` Eric Dumazet
2012-09-02 23:23           ` Eric Dumazet
2012-09-03  0:18             ` Dave Taht [this message]
2012-08-31 16:40   ` Jim Gettys
2012-08-31 16:49     ` Jonathan Morton
2012-08-31 17:15       ` Jim Gettys
2012-08-31 17:31         ` Rick Jones
2012-08-31 17:44           ` Jim Gettys

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=CAA93jw4igKGLWCd5SFuuRGhSef4MQhJRjGSrBUmbmQg4J_U3Jg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=codel@lists.bufferbloat.net \
    --cc=eric.dumazet@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