From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Mel Gorman <mel@skynet.ie>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"apw@shadowen.org" <apw@shadowen.org>,
Andrew Morton <akpm@linux-foundation.org>,
nickpiggin@yahoo.com.au, Christoph Lameter <clameter@sgi.com>
Subject: Re: [RFC][PATCH] zone config patch set [2/2] CONFIG_ZONE_MOVABLE
Date: Tue, 24 Jul 2007 10:28:42 +0900 [thread overview]
Message-ID: <20070724102842.bf470561.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20070723134517.GA15510@skynet.ie>
On Mon, 23 Jul 2007 14:45:17 +0100
mel@skynet.ie (Mel Gorman) wrote:
> > - return 0;
> > + return is_configured_zone(ZONE_HIGHMEM) &&
> > + is_configured_zone(ZONE_MOVABLE) &&
> > + (movable_zone == ZONE_HIGHMEM);
> > }
>
> I think this should remain inside the check for
> CONFIG_ARCH_POPULATES_NODE_MAP . movable_zone is not defined if it is
> not set. While this works with a cross-compiler for ARM (doesn't use
> CONFIG_ARCH_POPULATES_NODE_MAP), it's because the optimiser is getting
> rid of the references as opposed to the code being correct.
Hmm, ok.
> > +
> > +config ZONE_MOVABLE
> > + bool "A zone for movable pages"
> > + depends on ARCH_POPULATES_NODE_MAP
> > + help
> > + Allows creating a zone type only for movable pages, i.e page cache
>
> e.g. instead of i.e. here
>
> i.e. implies that only page cache and anonymous memory can use the zone.
> e.g. implies that page cache and anonymous memory are just two types
> that can use it.
>
> > + and anonymous memory. Because movable pages are to end to be easily
>
> Because movable pages are easily reclaimed .....
>
> > + reclaimed and page migration technique can move them, your chance
> > + for allocating big size memory will be better in this zone than
>
> allocating contiguous memory such as huge pages will be better ....
>
thanks, I'll merge above comments.
> > + if (!is_configured_zone(ZONE_MOVABLE)) {
> > + printk ("ZONE_MOVABLE is not configured, kernelcore= is ignored.\n");
> > + return 0;
> > + }
>
> This is a good check but bear in mind that in 2.6.23-rc1, this block of
> code looks different and there is both cmdline_parse_kernelcore() and
> cmdline_parse_movablecore().
>
yes. ok. I'll rebase.
Thank you.
-Kame
--
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:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-07-24 1:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-21 7:00 [RFC][PATCH] zone config patch set [1/2] zone ifdef cleaunp by renumbering KAMEZAWA Hiroyuki
2007-07-21 7:03 ` [RFC][PATCH] zone config patch set [2/2] CONFIG_ZONE_MOVABLE KAMEZAWA Hiroyuki
2007-07-23 7:25 ` Nick Piggin
2007-07-23 13:45 ` Mel Gorman
2007-07-24 1:28 ` KAMEZAWA Hiroyuki [this message]
2007-07-23 7:22 ` [RFC][PATCH] zone config patch set [1/2] zone ifdef cleaunp by renumbering Nick Piggin
2007-07-24 2:26 ` KAMEZAWA Hiroyuki
2007-07-23 13:16 ` 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=20070724102842.bf470561.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.org \
--cc=mel@skynet.ie \
--cc=nickpiggin@yahoo.com.au \
/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