mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: cl@linux-foundation.org
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	Tejun Heo <tj@kernel.org>,
	rusty@rustcorp.com.au, davem@davemloft.net,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [this_cpu_xx V3 00/19] Introduce per cpu atomic operations and avoid per cpu address arithmetic
Date: Fri, 2 Oct 2009 11:29:54 +0200	[thread overview]
Message-ID: <20091002092954.GA20779@elte.hu> (raw)
In-Reply-To: <20091001174033.576397715@gentwo.org>


* cl@linux-foundation.org <cl@linux-foundation.org> wrote:

> V2->V3:
> - Available via git tree against latest upstream from
> 	 git://git.kernel.org/pub/scm/linux/kernel/git/christoph/percpu.git linus
> - Rework SLUB per cpu operations. Get rid of dynamic DMA slab creation
>   for CONFIG_ZONE_DMA
> - Create fallback framework so that 64 bit ops on 32 bit platforms
>   can fallback to the use of preempt or interrupt disable. 64 bit
>   platforms can use 64 bit atomic per cpu ops.

I'm going to ask you (again...) to post future versions of this patchset 
to lkml.

linux-mm is a limited forum and a lot of people who might be interested 
in percpu matters simply wont know about your patch-set. per-cpu is not 
just a VM matter, obviously - it affects architectures, core kernel 
code, etc. etc.

I happened to see your patch-set and have a couple of comments about it 
but i will wait with discussing the issues until you submit these 
patches properly.

Thanks,

	Ingo

       reply	other threads:[~2009-10-02  9:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20091001174033.576397715@gentwo.org>
2009-10-02  9:29 ` Ingo Molnar [this message]
2009-10-02  9:31   ` Ingo Molnar

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=20091002092954.GA20779@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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
all inboxes | Powered by JetHome®