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>
Subject: [PATCH 0/4] create mm/Kconfig to detangle NUMA/DISCONTIG
Date: Mon, 04 Apr 2005 10:50:04 -0700 [thread overview]
Message-ID: <1112637004.27328.24.camel@localhost> (raw)
The end goal of these particular patches is to allow us to get some
small bits of global mm/ code compiled for either NUMA or DISCONTIGMEM.
Obviously, this alone doesn't justify messing with each architecture's
Kconfig file. Think of the 4th patch as one example of how this new
file can be used. We'll also be using it shortly for all of the page
migration and memory hotplug options. It just starts to look silly when
you have a patch to add the exact same Kconfig option to four or five
different architectures.
Compile tested for 27 different .config configurations on 5 different
architectures.
-- 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>
reply other threads:[~2005-04-04 17:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1112637004.27328.24.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=akpm@osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox