From: Nigel Cunningham <ncunningham@cyclades.com>
To: Mel Gorman <mel@csn.ul.ie>
Cc: davej@codemonkey.org.uk, tony.luck@intel.com,
linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
bob.picco@hp.com, ak@suse.de, linux-mm@kvack.org
Subject: Re: [PATCH 0/7] [RFC] Sizing zones and holes in an architecture independent manner V2
Date: Sat, 15 Apr 2006 09:17:04 +1000 [thread overview]
Message-ID: <200604150917.10596.ncunningham@cyclades.com> (raw)
In-Reply-To: <20060412232036.18862.84118.sendpatchset@skynet>
[-- Attachment #1: Type: text/plain, Size: 365 bytes --]
Hi Mel.
It looks to me like this code could be used by the software suspend code in
our determinations of what pages to save, particularly in the context of
memory hotplug support. Just some food for thought at the moment; I'll see if
I can come up with a patch when I have some time, but it might help justify
getting this merged.
Regards,
Nigel
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-04-14 23:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-12 23:20 Mel Gorman
2006-04-12 23:20 ` [PATCH 1/7] Introduce mechanism for registering active regions of memory Mel Gorman
2006-04-12 23:21 ` [PATCH 2/7] Have Power use add_active_range() and free_area_init_nodes() Mel Gorman
2006-04-12 23:21 ` [PATCH 3/7] Have x86 use add_active_range() and free_area_init_nodes Mel Gorman
2006-04-12 23:21 ` [PATCH 4/7] Have x86_64 " Mel Gorman
2006-04-12 23:22 ` [PATCH 5/7] Have ia64 " Mel Gorman
2006-04-12 23:22 ` [PATCH 6/7] Break out memory initialisation code from page_alloc.c to mem_init.c Mel Gorman
2006-04-12 23:22 ` [PATCH 7/7] Print out debugging information during initialisation Mel Gorman
2006-04-12 23:53 ` [PATCH 0/7] [RFC] Sizing zones and holes in an architecture independent manner V2 Andi Kleen
2006-04-13 0:22 ` Mel Gorman
2006-04-13 0:56 ` Andi Kleen
2006-04-13 1:08 ` Dave Hansen
2006-04-13 10:24 ` Mel Gorman
2006-04-13 9:52 ` Mel Gorman
2006-04-13 10:32 ` Yasunori Goto
2006-04-13 10:51 ` Mel Gorman
2006-04-13 17:19 ` Luck, Tony
2006-04-13 17:30 ` Mel Gorman
2006-04-13 17:47 ` Luck, Tony
2006-04-13 19:14 ` Mel Gorman
2006-04-13 21:53 ` Luck, Tony
2006-04-14 13:12 ` Mel Gorman
2006-04-14 20:53 ` Luck, Tony
2006-04-14 22:54 ` Mel Gorman
2006-04-14 23:17 ` Nigel Cunningham [this message]
2006-04-14 23:50 ` 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=200604150917.10596.ncunningham@cyclades.com \
--to=ncunningham@cyclades.com \
--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