lkml.org 
[lkml]   [2010]   [Jun]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH v2 1/2] tmpfs: Quick token library to allow scalable retrieval of tokens from token jar
From
Date
On Fri, 2010-06-11 at 14:52 -0700, Andrew Morton wrote:
> On Thu, 10 Jun 2010 10:06:14 -0700
> Tim Chen <tim.c.chen@linux.intel.com> wrote:
>
> > On Wed, 2010-06-09 at 15:36 -0700, Andrew Morton wrote:
> >
> > > >
> > > > You need some synchronization, otherwise the accounting
> > > > would not be exact and you could overflow. Yes you could
> > > > open code it, but having it in a library is nicer.
> > >
> > > The code doesn't have synchronisation! qtoken_return() can modify the
> > > per-cpu "cache" in parallel with qtoken_avail()'s walk across the
> > > per-cpu "caches", yielding an inaccurate result.
> > >
> > > This is all the same as percpu_add() executing in parallel with
> > > percpu_counter_sum() or percpu_counter_sum_positive().
> > >
> > > If we cannot tolerate that inaccuracy then these patches are no good
> > > and we need a rethink.
> > >
> > > If we _can_ tolerate that inaccuracy then percpu_counters can be used
> > > here. And doing that is preferable to reinventing percpu_counters
> > > badly.
> > >
> > > I'm just not seeing it.
> >
> >
> > The first version of the patch does a qtoken_reap_cache to reap the
> > tokens into pool before doing an accounting of the tokens and the token
> > count will be precise. It was not done in the second version of the
> > patch due to objection that it may be costly, and also the tokens count
> > will be fluctuating anyway. However, qtoken_avail is not called very
> > often (usually caller will use qtoken_get to access the tokens and it
> > will not need a total accounting of the tokens). We can do it the
> > previous way and there will be no inaccuracies.
> >
>
> afacit, your proposed implementation could have used percpu_counters.
> If so, that would be by far the best way of doing it, because that
> doesn't require the addition of new infrastructure.

Just having percpu counters is not enough.
There is additional logic required to manage the per cpu counters:
(1) set limit on the total number of tokens (2) distribute tokens into
per cpu counter (3) logic to coordinate where to get additional tokens
when we run out of tokens in the per cpu counter. (4) rebalance the
tokens when we have too many of the tokens returned to a per cpu
counter. I'm trying to encapsulate these logic into the library.
Otherwise, these logic will still need to be duplicated in the code
using the per cpu counters.

Tim



\
 
 \ /
  Last update: 2010-06-12 00:11    [from the cache]
©2003-2011 Jasper Spaans