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, 5 May 2012 10:22:31 -0700	[thread overview]
Message-ID: <CAA93jw4TZj8u3xxB364suwVA1qJ96vQUu79VEFKt6m+q07gyUQ@mail.gmail.com> (raw)
In-Reply-To: <1336237654.3752.524.camel@edumazet-glaptop>

On Sat, May 5, 2012 at 10:07 AM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
> On Sat, 2012-05-05 at 09:11 -0700, Dave Taht wrote:
>> Nice!
>>
>> Nits:
>>
>> 0) I figure you already have an iproute2 patch that you can send?
>>     I thought 5 hours ago I had almost, but not entirely grokked netlink.
>>     The way you just did it was not at all how I thought it worked. :/
>>     but I will read.
>
>
> I'll send it ( I am currently with friends ...), but you dont need it to
> use codel with default params :
>
> qdisc add dev $DEV parent 1:1 handle 10: est 1sec 4sec codel

yep.

>> 1) I take it if a limit is not specified or set here, sch->limit comes
>> from txqueuelen?
>
> No, you set a default limit of 1000 in your patch

If I didn't set that at all, where does it come from?

(never mind I can find it, enjoy your saturday!)

>
>>     I do kind of like infinite queues (and angels dancing on the heads of pins)
>> 2) I woke up with a mod that could do ecn. I'll do an rfc patch
>
> Not sure it can play, if all packets are ECN, you need to drop at some
> point.

Yea, that's where blue had a few ideas, but the right thing is to setup
some long rtts and see what happens.

>> .
>> 3) Tom's already on the list
> ok
>> 4) I'd like to play with this a lot (and have others do so too) before
>> it goes upstream,
>>     gain kathie and vans blessing, etc. Couple weeks? (see 2). In
>> particular I was
>>     hoping to see actual pings under load match the target setting.
>> I'll get this
>>     going on two boxes and see what happens... play with bql, htb, etc...
>
> Hey, you'll send the patch when ready.

ok!

>
>> 5) thought the * 16 could be efficiently implemented by the compiler,
>> and saves a mem
>>     access.
>
> Well, just see the code on x86_32, the ktime conversion is expensive.
> Access to memory is free since cache line is already in cpu cache.

on everything but the x86_32 (do people still use that? :)). I would think
on the x86_64 and mips (16 bit memory bus) would be cheaper...
but it's rather a nit regardless.

>
> By the way, I found the precalculated array of 64 values is not really
> useful, we have q->count > 64 most of the time with 2 flows.

yea, just noticed that. I figured 25 wasn't enough, didn't think 64 was
either. will get some data on various flows and find a better value.

>
>> 6) unless 2) happens we can kill q->flags
>
> Yes

Enjoy your saturday!
>
>
>



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

  reply	other threads:[~2012-05-05 17:22 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 [this message]
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
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=CAA93jw4TZj8u3xxB364suwVA1qJ96vQUu79VEFKt6m+q07gyUQ@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