From: Ingo Molnar <mingo@elte.hu>
To: Tejun Heo <tj@kernel.org>
Cc: cl@linux-foundation.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, rusty@rustcorp.com.au,
Pekka Enberg <penberg@cs.helsinki.fi>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [this_cpu_xx V4 00/20] Introduce per cpu atomic operations and avoid per cpu address arithmetic
Date: Fri, 2 Oct 2009 11:54:55 +0200 [thread overview]
Message-ID: <20091002095455.GC21427@elte.hu> (raw)
In-Reply-To: <4AC5C836.8000502@kernel.org>
* Tejun Heo <tj@kernel.org> wrote:
> Hello,
>
> cl@linux-foundation.org wrote:
> > V3->V4:
> > - Fix various macro definitions.
> > - Provider experimental percpu based fastpath that does not disable
> > interrupts for SLUB.
>
> The series looks very good to me. [...]
Seconded, very nice series!
One final step/cleanup seems to be missing from it: it should replace
current uses of percpu_op() [percpu_read(), etc.] in the x86 tree and
elsewhere with the new this_cpu_*() primitives. this_cpu_*() is using
per_cpu_from_op/per_cpu_to_op directly, we dont need those percpu_op()
variants anymore.
There should also be a kernel image size comparison done for that step,
to make sure all the new primitives are optimized to the max on the
instruction level.
> [...] percpu#for-next now has ia64 bits included and the legacy
> allocator is gone there so it can carry this series. Sans the last
> one, they seem they can be stable and incremental from now on, right?
> Shall I include this series into the percpu tree?
I'd definitely recommend doing that - it should be tested early and wide
for v2.6.33, and together with other percpu bits.
Ingo
next prev parent reply other threads:[~2009-10-02 9:55 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 21:25 cl
2009-10-01 21:25 ` [this_cpu_xx V4 01/20] Introduce this_cpu_ptr() and generic this_cpu_* operations cl
2009-10-02 9:16 ` Tejun Heo
2009-10-02 9:34 ` Ingo Molnar
2009-10-02 17:11 ` Christoph Lameter
2009-10-06 10:04 ` Rusty Russell
2009-10-06 23:39 ` Christoph Lameter
2009-10-06 23:55 ` Tejun Heo
2009-10-08 17:57 ` [Patchs vs. percpu-next] Use this_cpu_xx to dynamically allocate counters Christoph Lameter
2009-10-13 11:51 ` Rusty Russell
2009-10-08 18:06 ` Christoph Lameter
2009-10-01 21:25 ` [this_cpu_xx V4 02/20] this_cpu: X86 optimized this_cpu operations cl
2009-10-02 9:18 ` Tejun Heo
2009-10-02 9:59 ` Ingo Molnar
2009-10-03 19:33 ` Pekka Enberg
2009-10-04 16:47 ` Ingo Molnar
2009-10-04 16:51 ` Pekka Enberg
2009-10-01 21:25 ` [this_cpu_xx V4 03/20] Use this_cpu operations for SNMP statistics cl
2009-10-01 21:25 ` [this_cpu_xx V4 04/20] Use this_cpu operations for NFS statistics cl
2009-10-01 21:25 ` [this_cpu_xx V4 05/20] use this_cpu ops for network statistics cl
2009-10-01 21:25 ` [this_cpu_xx V4 06/20] this_cpu_ptr: Straight transformations cl
2009-10-01 21:25 ` [this_cpu_xx V4 07/20] this_cpu_ptr: Eliminate get/put_cpu cl
2009-10-01 21:25 ` [this_cpu_xx V4 08/20] this_cpu_ptr: xfs_icsb_modify_counters does not need "cpu" variable cl
2009-10-01 21:25 ` [this_cpu_xx V4 09/20] Use this_cpu_ptr in crypto subsystem cl
2009-10-01 21:25 ` [this_cpu_xx V4 10/20] Use this_cpu ops for VM statistics cl
2009-10-01 21:25 ` [this_cpu_xx V4 11/20] RCU: Use this_cpu operations cl
2009-10-03 10:52 ` Tejun Heo
2009-10-01 21:25 ` [this_cpu_xx V4 12/20] Move early initialization of pagesets out of zone_wait_table_init() cl
2009-10-02 14:16 ` Mel Gorman
2009-10-02 17:30 ` Christoph Lameter
2009-10-05 9:35 ` Mel Gorman
2009-10-03 10:29 ` Tejun Heo
2009-10-05 14:39 ` Christoph Lameter
2009-10-05 15:01 ` Tejun Heo
2009-10-05 15:06 ` Christoph Lameter
2009-10-05 15:21 ` Tejun Heo
2009-10-05 15:28 ` Christoph Lameter
2009-10-05 15:41 ` Tejun Heo
2009-10-05 15:39 ` Christoph Lameter
2009-10-01 21:25 ` [this_cpu_xx V4 13/20] this_cpu_ops: page allocator conversion cl
2009-10-02 15:14 ` Mel Gorman
2009-10-02 17:39 ` Christoph Lameter
2009-10-05 9:45 ` Mel Gorman
2009-10-05 14:43 ` Christoph Lameter
2009-10-05 14:55 ` Christoph Lameter
2009-10-06 9:45 ` Mel Gorman
2009-10-06 16:34 ` Christoph Lameter
2009-10-06 17:03 ` Mel Gorman
2009-10-06 17:51 ` Christoph Lameter
2009-10-06 18:36 ` Mel Gorman
2009-10-06 19:06 ` Christoph Lameter
2009-10-07 10:42 ` Mel Gorman
2009-10-01 21:25 ` [this_cpu_xx V4 14/20] this_cpu ops: Remove pageset_notifier cl
2009-10-01 21:25 ` [this_cpu_xx V4 15/20] Use this_cpu operations in slub cl
2009-10-01 21:25 ` [this_cpu_xx V4 16/20] SLUB: Get rid of dynamic DMA kmalloc cache allocation cl
2009-10-01 21:25 ` [this_cpu_xx V4 17/20] this_cpu: Remove slub kmem_cache fields cl
2009-10-01 21:25 ` [this_cpu_xx V4 18/20] Make slub statistics use this_cpu_inc cl
2009-10-01 21:25 ` [this_cpu_xx V4 19/20] this_cpu: slub aggressive use of this_cpu operations in the hotpaths cl
2009-10-01 21:25 ` [this_cpu_xx V4 20/20] SLUB: Experimental new fastpath w/o interrupt disable cl
2009-10-02 9:30 ` [this_cpu_xx V4 00/20] Introduce per cpu atomic operations and avoid per cpu address arithmetic Tejun Heo
2009-10-02 9:54 ` Ingo Molnar [this message]
2009-10-02 17:15 ` Christoph Lameter
2009-10-02 17:32 ` Ingo Molnar
2009-10-02 17:49 ` Christoph Lameter
2009-10-02 17:10 ` Christoph Lameter
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091002095455.GC21427@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=rusty@rustcorp.com.au \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
/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
Powered by JetHome