Messages in this thread | | | Date | Mon, 21 Dec 2009 17:19:15 +0900 | From | Tejun Heo <> | Subject | Re: [this_cpu_xx V8 07/16] Module handling: Use this_cpu_xx to dynamically allocate counters |
| |
On 12/21/2009 04:59 PM, Tejun Heo wrote: > Here's the version I committed to percpu branch. > > Thanks. > > From 8af47ddd01364ae3c663c0bc92415c06fe887ba1 Mon Sep 17 00:00:00 2001 > From: Christoph Lameter <cl@linux-foundation.org> > Date: Fri, 18 Dec 2009 16:26:24 -0600 > Subject: [PATCH] module: Use this_cpu_xx to dynamically allocate counters > > Use cpu ops to deal with the per cpu data instead of a local_t. Reduces memory > requirements, cache footprint and decreases cycle counts. > > The this_cpu_xx operations are also used for !SMP mode. Otherwise we could > not drop the use of __module_ref_addr() which would make per cpu data handling > complicated. this_cpu_xx operations have their own fallback for !SMP. > > The last hold out of users of local_t is the tracing ringbuffer after this patch > has been applied. > > Signed-off-by: Christoph Lameter <cl@linux-foundation.org> > Cc: Rusty Russell <rusty@rustcorp.com.au>
This was changed to Acked-by as Rusty acked on the previous thread.
Thanks.
-- tejun
| |