From: Dave Hansen <haveblue@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-mm <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Martin J. Bligh" <mbligh@aracnet.com>,
Andy Whitcroft <apw@shadowen.org>
Subject: [PATCH 0/3] refactor i386 memory setup
Date: Fri, 04 Feb 2005 13:05:55 -0800 [thread overview]
Message-ID: <1107551155.9084.27.camel@localhost> (raw)
The following 3 patches help to make some of the i386 NUMA code a bit
more manageable, and remove a lot of duplicate code in the process. All
3 together were test-booted on a NUMA-Q, Summit, and a regular old
laptop.
They're in no hurry to get merged, and could wait for the 2.6.12 series.
-- Dave
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <haveblue@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-mm <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Martin J. Bligh" <mbligh@aracnet.com>,
Andy Whitcroft <apw@shadowen.org>
Subject: [PATCH 0/3] refactor i386 memory setup
Date: Fri, 04 Feb 2005 13:05:55 -0800 [thread overview]
Message-ID: <1107551155.9084.27.camel@localhost> (raw)
The following 3 patches help to make some of the i386 NUMA code a bit
more manageable, and remove a lot of duplicate code in the process. All
3 together were test-booted on a NUMA-Q, Summit, and a regular old
laptop.
They're in no hurry to get merged, and could wait for the 2.6.12 series.
-- 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 reply other threads:[~2005-02-04 21:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 21:05 Dave Hansen [this message]
2005-02-04 21:05 ` [PATCH 0/3] refactor i386 memory setup Dave Hansen
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=1107551155.9084.27.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--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 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.