From: Andrew Morton <akpm@osdl.org>
To: Mel Gorman <mel@csn.ul.ie>
Cc: davej@codemonkey.org.uk, tony.luck@intel.com, linux-mm@kvack.org,
mel@csn.ul.ie, ak@suse.de, bob.picco@hp.com,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 0/5] Sizing zones and holes in an architecture independent manner V7
Date: Tue, 6 Jun 2006 16:43:11 -0700 [thread overview]
Message-ID: <20060606164311.27d4af98.akpm@osdl.org> (raw)
In-Reply-To: <20060606134710.21419.48239.sendpatchset@skynet.skynet.ie>
On Tue, 6 Jun 2006 14:47:10 +0100 (IST)
Mel Gorman <mel@csn.ul.ie> wrote:
> This is V7 of the patchset to size zones and memory holes in an
> architecture-independent manner.
I hope this won't deprive me of my 4 kbyte highmem zone.
I won't merge these patches for rc6-mm1 - we already have a few problems in
this area which I don't think anyone understands yet.
next prev parent reply other threads:[~2006-06-06 23:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 13:47 [PATCH 0/5] Sizing zones and holes in an architecture independent manner V7 Mel Gorman
2006-06-06 13:47 ` [PATCH 1/5] Introduce mechanism for registering active regions of memory Mel Gorman
2006-06-06 13:47 ` [PATCH 2/5] Have Power use add_active_range() and free_area_init_nodes() Mel Gorman
2006-06-06 13:48 ` [PATCH 3/5] Have x86 use add_active_range() and free_area_init_nodes Mel Gorman
2006-06-06 13:48 ` [PATCH 4/5] Have x86_64 " Mel Gorman
2006-06-06 13:48 ` [PATCH 5/5] Have ia64 " Mel Gorman
2006-06-06 23:43 ` Andrew Morton [this message]
2006-06-07 9:42 ` [PATCH 0/5] Sizing zones and holes in an architecture independent manner V7 Mel Gorman
2006-06-07 9:45 ` Andi Kleen
2006-06-07 10:11 ` Mel Gorman
2006-06-07 10:16 ` Andi Kleen
2006-06-07 10:54 ` Mel Gorman
2006-06-07 15:20 ` Andi Kleen
2006-06-07 16:25 ` Mel Gorman
2006-06-09 12:57 ` Mel Gorman
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=20060606164311.27d4af98.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ak@suse.de \
--cc=bob.picco@hp.com \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mel@csn.ul.ie \
--cc=tony.luck@intel.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).