From: Dave Hansen <haveblue@us.ibm.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re: [RFC][PATCH 0/5] consolidate i386 NUMA init code
Date: Wed, 26 Jan 2005 10:01:49 -0800 [thread overview]
Message-ID: <1106762509.6093.67.camel@localhost> (raw)
In-Reply-To: <15640000.1106750236@flay>
On Wed, 2005-01-26 at 06:37 -0800, Martin J. Bligh wrote:
> > The following five patches reorganize and consolidate some of the i386
> > NUMA/discontigmem code. They grew out of some observations as we
> > produced the memory hotplug patches.
> >
> > Only the first one is really necessary, as it makes the implementation
> > of one of the hotplug components much simpler and smaller. 2 and 3 came
> > from just looking at the effects on the code after 1.
> >
> > 4 and 5 aren't absolutely required for hotplug either, but do allow
> > sharing a bunch of code between the normal boot-time init and hotplug
> > cases.
> >
> > These are all on top of 2.6.11-rc2-mm1.
>
> Looks reasonable. How much testing have they had, on what platforms?
Built on all the i386 configs here:
http://sr71.net/patches/2.6.11/2.6.11-rc1-mm1-mhp1/configs/
Booted on x440 (summit and generic), numaq, 4-way PIII. I would imagine
that any problem would manifest as the system simply not booting. The
most likely to fail would be systems with DISCONTIG enabled, because
that's where the greatest amount of churn happened. The normal !
DISCONTIG case still uses most of the same code.
Anyway, I think they're probably ready for a run in -mm, with the "if
the machines don't boot check these first" flag set. Although, I'd
appreciate any other testing that anyone wants to throw at them.
-- Dave
--
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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2005-01-26 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 0:23 Dave Hansen
2005-01-26 14:37 ` Martin J. Bligh
2005-01-26 18:01 ` Dave Hansen [this message]
2005-01-26 17:53 ` Martin J. Bligh
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=1106762509.6093.67.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@aracnet.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