[lkml]   [2008]   [Mar]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] alloc_percpu() fails to allocate percpu data
On 2/21/08, Eric Dumazet <> wrote:
> Some oprofile results obtained while using tbench on a 2x2 cpu machine
> were very surprising.
> For example, loopback_xmit() function was using high number of cpu
> cycles to perform
> the statistic updates, supposed to be real cheap since they use percpu data
> pcpu_lstats = netdev_priv(dev);
> lb_stats = per_cpu_ptr(pcpu_lstats, smp_processor_id());
> lb_stats->packets++; /* HERE : serious contention */
> lb_stats->bytes += skb->len;
> struct pcpu_lstats is a small structure containing two longs. It appears
> that on my 32bits platform,
> alloc_percpu(8) allocates a single cache line, instead of giving to
> each cpu a separate
> cache line.
> Using the following patch gave me impressive boost in various benchmarks
> ( 6 % in tbench)
> (all percpu_counters hit this bug too)
> Long term fix (ie >= 2.6.26) would be to let each CPU allocate their own
> block of memory, so that we
> dont need to roudup sizes to L1_CACHE_BYTES, or merging the SGI stuff of
> course...
> Note : SLUB vs SLAB is important here to *show* the improvement, since
> they dont have the same minimum
> allocation sizes (8 bytes vs 32 bytes).
> This could very well explain regressions some guys reported when they
> switched to SLUB.

I see that this fix was committed to mainline as commit

The commit didn't "Cc: <>", and it doesn't appear to
be queued for 2.6.24.x. Should it be?

If I understand you correctly, SLAB doesn't create this particular
cache thrashing on 32bit systems? Is SLAB ok on other architectures
too? Can you (or others) comment on the importance of this fix
relative to x86_64 (64byte cacheline) and SLAB?

I'm particularly interested in this given the use of percpu_counters
with the per bdi write throttling.


 \ /
  Last update: 2008-03-11 19:19    [W:0.136 / U:17.052 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site