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: [Codel] failing, bailing
Date: Sat, 5 May 2012 19:27:25 -0700	[thread overview]
Message-ID: <CAA93jw6GjRbaf7hNEDmPyngYj0=nz_R9SLuJ2aS6-3w227VCig@mail.gmail.com> (raw)

So I got caught up to patch v6 and the latest iproute code from eric
also on this list, got some dinner, and tried again.

Failed.

Lastest kernel patch is here:

https://lists.bufferbloat.net/private/codel/2012-May/000073.html
https://lists.bufferbloat.net/private/codel/2012-May/000076.html

And the current iproute2 patch is here:

https://lists.bufferbloat.net/private/codel/2012-May/000074.html

On Sat, May 5, 2012 at 4:19 PM, dave taht <dave.taht@gmail.com> wrote:
> On 05/05/2012 04:07 PM, Eric Dumazet wrote:
>> This part of Codel seems suspicious (last page )
>>
>> // If min went above target close to when we last went below it
>> // assume that the drop rate that controlled the queue on the
>> // last cycle is a good starting point to control it now.
>> if (now - drop_next<  16.*interval) {
>>        int c = count - 1;
>>        count = c<1? 1 : c;
>> else {
>>        count = 1;
>> }
>>
>>
>> I suggest to replace it by a more conservative algo :
>>
>> // If min went above target close to when we last went below it
>> // assume that sqrt(half) the drop rate that controlled the queue on the
>> // last cycle is a good starting point to control it now.
>> if (now - drop_next<  16.*interval) {
>>        int c = count>>  1;
>>        count = c<1? 1 : c;
>> else {
>>        count = 1;
>> }
>>
> I don't buy it. See previous mail.

OK, but I rented the idea. Against about 30 streams I get this...

$TC -s qdisc show dev eth0
qdisc codel 8007: root refcnt 2 limit 1000p minbytes 1514 target 5.0ms
interval 100.0ms
 Sent 1710602931 bytes 1217897 pkt (dropped 32097, overlimits 0
requeues 520278)
 backlog 112036b 75p requeues 520278
  count 2784 delay 9.0ms drop_next 489us

> count - some_x sure.

Worse.

Then I tried tossing this in everywhere there was a >, to increase
the granularity of the comparison to 10us

static inline int ktime_compare_us10(ktime_t lhs, const ktime_t rhs)
{
        return(ktime_compare(ktime_add_ns(lhs,10000),rhs));
}

need to sanitize all the comparisons tho... but I'm...

Giving up. Calling in the gods. Tossing the preso on my kindle and
calling it a day.

>
>
>> With this change, my q->count max value is 12000
>>
>>
>>
>



-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net

                 reply	other threads:[~2012-05-06  2:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAA93jw6GjRbaf7hNEDmPyngYj0=nz_R9SLuJ2aS6-3w227VCig@mail.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