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, "Dave Täht" <dave.taht@bufferbloat.net>
Subject: Re: [Codel] [PATCH v5] pkt_sched: codel: Controlled Delay AQM
Date: Sat, 05 May 2012 15:15:01 -0700	[thread overview]
Message-ID: <4FA5A665.4090708@gmail.com> (raw)
In-Reply-To: <1336255783.3752.573.camel@edumazet-glaptop>

On 05/05/2012 03:09 PM, Eric Dumazet wrote:
> On Sat, 2012-05-05 at 15:03 -0700, dave taht wrote:
>
>> Maybe on your arch, but highly doubtful on a 680Mhz mips that isn't even
>> superscalar.
>>
> CPU are fast, memory is slow.
>
>> I'd prefer to leave it in and be able to compile it out, and actually
>> measure the difference.
> You optimize the case where there is no need to optimize (small queue)
>
> I can see count bigger than 100000 with 20 concurrent netperf
At what speeds?

Are you testing 10GigE? I'm dying to know what happens there...

If I could encourage you to ratchet down to 2 or 100Mbit
it would be easier to get comparable results.

I like using the ethtool trick for 10 and 100Mbit as that
leaves just bql and the qdisc in the mix.

We've discussed elsewhere some of the issues with htb.

Also I'd had an 'interesting' result at 2Mbit that I haven't had time
to duplicate, which I'm going to do now on mainstream hardware.

> This makes no sense to have a cache so big.
concur, which is why I'd also asked how big it got, and how fast you 
were running

>  Or there is a bug in codel


hmm.

>
>
>


  parent reply	other threads:[~2012-05-05 22:15 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-05 11:34 [Codel] [PATCH 2/2] Clamp interval to 32 bits Dave Täht
2012-05-05 11:40 ` Dave Taht
2012-05-05 11:53   ` Eric Dumazet
2012-05-05 14:49     ` [Codel] [PATCH v5] pkt_sched: codel: Controlled Delay AQM Eric Dumazet
2012-05-05 16:11       ` Dave Taht
2012-05-05 17:07         ` Eric Dumazet
2012-05-05 17:22           ` Dave Taht
2012-05-05 18:54             ` [Codel] [PATCH iproute2] " Eric Dumazet
2012-05-05 19:08               ` Eric Dumazet
2012-05-05 21:30               ` Eric Dumazet
2012-05-06 18:56                 ` [Codel] [PATCH v8 " Eric Dumazet
2012-05-05 20:20       ` [Codel] [PATCH v5] pkt_sched: " Eric Dumazet
2012-05-05 20:36         ` Eric Dumazet
2012-05-05 21:11           ` Eric Dumazet
2012-05-05 21:12             ` dave taht
2012-05-05 21:20               ` Eric Dumazet
2012-05-05 21:28                 ` [Codel] [PATCH v6] " Eric Dumazet
2012-05-05 21:40                   ` Eric Dumazet
2012-05-05 21:58                   ` Eric Dumazet
2012-05-06 18:52                   ` [Codel] [PATCH v8] " Eric Dumazet
2012-05-06 19:51                     ` Eric Dumazet
2012-05-05 22:03                 ` [Codel] [PATCH v5] " dave taht
2012-05-05 22:09                   ` Eric Dumazet
2012-05-05 22:12                     ` Eric Dumazet
2012-05-05 22:16                       ` dave taht
2012-05-05 22:15                     ` dave taht [this message]
2012-05-05 22:34                     ` dave taht
2012-05-05 22:39                       ` Eric Dumazet
2012-05-05 22:48                         ` dave taht
2012-05-05 23:07                           ` Eric Dumazet
2012-05-05 23:19                             ` dave taht
2012-05-06  5:18                               ` Eric Dumazet
2012-05-05 23:09                           ` dave taht
2012-05-05 23:15                             ` 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=4FA5A665.4090708@gmail.com \
    --to=dave.taht@gmail.com \
    --cc=codel@lists.bufferbloat.net \
    --cc=dave.taht@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