From: Eric Dumazet <eric.dumazet@gmail.com>
To: dave taht <dave.taht@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: Sun, 06 May 2012 00:39:14 +0200 [thread overview]
Message-ID: <1336257554.3752.578.camel@edumazet-glaptop> (raw)
In-Reply-To: <4FA5AB05.9030305@gmail.com>
On Sat, 2012-05-05 at 15:34 -0700, dave taht wrote:
> 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
> >
> > This makes no sense to have a cache so big.
> >
> > Or there is a bug in codel
> The original reciprocol approximation test code rapidly goes AWOL after
> exceeding 2^8.
>
> I went looking for butterflies and didn't see any in the scaled code in
> the range 0-100000,
> and they would only take flight briefly, so...
>
> However I have not corrected it for BITS_PER_LONG as per our 4AM
> discussion.
You should use the exact code in kernel. (using BITS_PER_LONG)
>
> ...
>
> interval/sqrt(99999)=316229 approx :6250190 19.76475908 interval/scaled:
> 316236 1.00002214
>
> >
> >
>
If you read the code , there is no possible overflow, even with very
large 'u32 count'
anyway the problem is q->count keeps increasing under load.
Only when load is stopped for a while, count is reset to 1
next prev parent reply other threads:[~2012-05-05 22:39 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
2012-05-05 22:34 ` dave taht
2012-05-05 22:39 ` Eric Dumazet [this message]
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=1336257554.3752.578.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=codel@lists.bufferbloat.net \
--cc=dave.taht@bufferbloat.net \
--cc=dave.taht@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