From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Dave Hansen <haveblue@us.ibm.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 09:53:39 -0800 [thread overview]
Message-ID: <2410000.1106762019@flay> (raw)
In-Reply-To: <1106762509.6093.67.camel@localhost>
> 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.
Yup, as long as they boot, is probably good enough for now.
Thanks,
M.
WARNING: multiple messages have this Message-ID (diff)
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Dave Hansen <haveblue@us.ibm.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 09:53:39 -0800 [thread overview]
Message-ID: <2410000.1106762019@flay> (raw)
In-Reply-To: <1106762509.6093.67.camel@localhost>
> 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.
Yup, as long as they boot, is probably good enough for now.
Thanks,
M.
--
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 23:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 0:23 [RFC][PATCH 0/5] consolidate i386 NUMA init code Dave Hansen
2005-01-26 0:23 ` Dave Hansen
2005-01-26 14:37 ` Martin J. Bligh
2005-01-26 14:37 ` Martin J. Bligh
2005-01-26 18:01 ` Dave Hansen
2005-01-26 18:01 ` Dave Hansen
2005-01-26 17:53 ` Martin J. Bligh [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=2410000.1106762019@flay \
--to=mbligh@aracnet.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.