[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110512090534.GE1030@htj.dyndns.org>
Date: Thu, 12 May 2011 11:05:34 +0200
From: Tejun Heo <tj@...nel.org>
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: Shaohua Li <shaohua.li@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"cl@...ux.com" <cl@...ux.com>,
"npiggin@...nel.dk" <npiggin@...nel.dk>
Subject: Re: [patch v2 0/5] percpu_counter: bug fix and enhancement
Hello,
On Thu, May 12, 2011 at 11:02:15AM +0200, Eric Dumazet wrote:
> > I don't think @maxfuzzy is necessary there. I wrote this before but
> > why can't we track the actual deviation instead of the number of
> > deviation events?
>
> Thats roughly same thing (BATCH multiplicator factor apart)
>
> Most percpu_counter users for a given percpu_counter object use a given
> BATCH, dont they ?
Well, @maxfuzzy is much harder than @batch. It's way less intuitive.
Although I haven't really thought about it that much, I think it might
be possible to eliminate it. Maybe I'm confused. I'll take another
look later but if someone can think of something, please jump right
in.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists