mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Paul Mackerras <paulus@samba.org>,
	Nick Piggin <nickpiggin@yahoo.com.au>,
	Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	Andi Kleen <ak@suse.de>,
	Martin Mares <mj@atrey.karlin.mff.cuni.cz>,
	bjornw@axis.com, schwidefsky@de.ibm.com,
	benedict.gaster@superh.com, lethal@linux-sh.org,
	Chris Zankel <chris@zankel.net>,
	Marc Gauthier <marc@tensilica.com>,
	Joe Taylor <joe@tensilica.com>,
	David Mosberger-Tang <davidm@hpl.hp.com>,
	rth@twiddle.net, spyro@f2s.com, starvik@axis.com,
	tony.luck@intel.com, linux-ia64@vger.kernel.org,
	ralf@linux-mips.org, linux-mips@linux-mips.org,
	grundler@parisc-linux.org, parisc-linux@parisc-linux.org,
	linuxppc-dev@ozlabs.org, linux390@de.ibm.com,
	davem@davemloft.net, arnd@arndb.de, kenneth.w.chen@intel.com,
	sam@ravnborg.org, kiran@scalex86.org
Subject: Re: [RFC PATCH 00/09] robust VM per_cpu variables
Date: Wed, 17 May 2006 08:49:08 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0605170846190.13337@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0605171104100.13160@gandalf.stny.rr.com>

On Wed, 17 May 2006, Steven Rostedt wrote:

> OK, now I'm just rambling. I don't know,  have any other ideas on making
> this more robust?  Or is this all in vain, and I should spend my evenings
> walking around this beautiful town of Karlsruhe ;)

Well I'd like to see a comprehensive solution including a fix for the 
problems with allocper_cpu() allocations (allocper_cpu has to allocate 
memory for potential processors... which could be a lot on 
some types of systems and its allocated somewhere not on the nodes of the 
processor since they may not yet be online).

Wish I could be back home in Germany to talk a walk with you. Are you 
coming to the OLS?


  reply	other threads:[~2006-05-17 15:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-17  9:54 Steven Rostedt
2006-05-17  9:56 ` [RFC PATCH 01/09] robust VM per_cpu core Steven Rostedt
2006-05-17  9:17   ` Andi Kleen
2006-05-17 10:46     ` Steven Rostedt
2006-05-17 11:08       ` Andi Kleen
2006-05-17 11:31         ` Steven Rostedt
2006-05-17  9:56 ` [RFC PATCH 01/09] robust VM per_cpu mm header update Steven Rostedt
2006-05-17  9:57 ` [RFC PATCH 03/09] robust VM per_cpu generic header Steven Rostedt
2006-05-17  9:58 ` [RFC PATCH 04/09] robust VM per_cpu main startup Steven Rostedt
2006-05-17  9:59 ` [RFC PATCH 05/09] robust VM per_cpu module Steven Rostedt
2006-05-17 10:00 ` [RFC PATCH 06/09] robust VM per_cpu i386 bootmem Steven Rostedt
2006-05-17 10:01 ` [RFC PATCH 07/09] robust VM per_cpu i386 VM area Steven Rostedt
2006-05-17 10:01 ` [RFC PATCH 08/09] robust VM per_cpu i386 header Steven Rostedt
2006-05-17 10:01 ` [RFC PATCH 09/09] robust VM per_cpu i386 Kconfig update Steven Rostedt
2006-05-17 14:52 ` [RFC PATCH 00/09] robust VM per_cpu variables Christoph Lameter
2006-05-17 15:18   ` Steven Rostedt
2006-05-17 15:49     ` Christoph Lameter [this message]
2006-05-17 15:56       ` Steven Rostedt
2006-05-17 17:40         ` Christoph Lameter
2006-05-18  7:00           ` Steven Rostedt

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=Pine.LNX.4.64.0605170846190.13337@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=arnd@arndb.de \
    --cc=benedict.gaster@superh.com \
    --cc=bjornw@axis.com \
    --cc=chris@zankel.net \
    --cc=davem@davemloft.net \
    --cc=davidm@hpl.hp.com \
    --cc=grundler@parisc-linux.org \
    --cc=joe@tensilica.com \
    --cc=kenneth.w.chen@intel.com \
    --cc=kiran@scalex86.org \
    --cc=lethal@linux-sh.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux390@de.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=marc@tensilica.com \
    --cc=mingo@elte.hu \
    --cc=mj@atrey.karlin.mff.cuni.cz \
    --cc=nickpiggin@yahoo.com.au \
    --cc=parisc-linux@parisc-linux.org \
    --cc=paulus@samba.org \
    --cc=ralf@linux-mips.org \
    --cc=rostedt@goodmis.org \
    --cc=rth@twiddle.net \
    --cc=rusty@rustcorp.com.au \
    --cc=sam@ravnborg.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=spyro@f2s.com \
    --cc=starvik@axis.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=torvalds@osdl.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®