linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: travis@sgi.com, Andi Kleen <ak@suse.de>,
	Eric Dumazet <dada1@cosmosbay.com>,
	Christoph Lameter <clameter@sgi.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] x86: Fixup NR-CPUS patch for numa
Date: Fri, 18 Jan 2008 13:08:40 +0100	[thread overview]
Message-ID: <20080118120840.GE11044@elte.hu> (raw)
In-Reply-To: <20080117103000.5e97dcd2.akpm@linux-foundation.org>

* Andrew Morton <akpm@linux-foundation.org> wrote:

> > Also, the mem -> node hash lookup is fixed.
> > 
> > Based on 2.6.24-rc6-mm1 + change-NR_CPUS-V3 patchset
> 
> hm, I've been hiding from those patches.
> 
> Are they ready?

i'm carrying them in x86.git, and they are pretty robust, with one 
outstanding build failure.

( and i've asked Mike for a CONFIG_SMP_MAX debug option that selects the
  baddest high-end features we have with 1024 or 4096 CPUs, etc. - this 
  way allyesconfig bootups will show us any problems on that scale of 
  the spectrum. )

	Ingo

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      parent reply	other threads:[~2008-01-18 12:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080116183438.506737000@sgi.com>
2008-01-16 18:34 ` [PATCH 1/1] x86: Fixup NR-CPUS patch for numa travis
2008-01-17 18:30   ` Andrew Morton
2008-01-17 18:51     ` Mike Travis
2008-01-18 12:08     ` Ingo Molnar [this message]

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=20080118120840.GE11044@elte.hu \
    --to=mingo@elte.hu \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=dada1@cosmosbay.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=travis@sgi.com \
    /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;
as well as URLs for NNTP newsgroup(s).