From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: lhms <lhms-devel@lists.sourceforge.net>, linux-mm <linux-mm@kvack.org>
Subject: Re: [Lhms-devel] [RFC] consistency of zone->zone_start_pfn, spanned_pages
Date: Tue, 17 May 2005 09:40:28 +0900 [thread overview]
Message-ID: <42893D7C.6070907@jp.fujitsu.com> (raw)
In-Reply-To: <1116000019.32433.10.camel@localhost>
Hi,
Dave Hansen wrote:
> The zone struct has a few important members which explicitly define the
> range of pages that it manages: zone_start_pfn and spanned_pages.
>
> The current memory hotplug coded has concentrated on appending memory to
> existing zones, which means just increasing spanned_pages. There is
> currently no code that breaks at runtime if this value is simply
> incremented.
>
How about removing zone_start_pfn and spanned_pages ?
I found they are used in
bad_range() in page_alloc.c
mark_free_page() in CONFIG_PM.
And I think we can remove them with section-range-ops when CONFIG_SPARSEMEM=y.
They are used in some another places ?
-- 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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2005-05-17 0:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 16:00 Dave Hansen
2005-05-13 18:24 ` Robin Holt
2005-05-13 18:31 ` Dave Hansen
2005-05-17 9:50 ` Andy Whitcroft
2005-05-17 10:46 ` Robin Holt
2005-05-17 0:40 ` KAMEZAWA Hiroyuki [this message]
2005-05-17 5:43 ` [Lhms-devel] " Yasunori Goto
2005-05-17 12:32 ` Andy Whitcroft
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=42893D7C.6070907@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=haveblue@us.ibm.com \
--cc=lhms-devel@lists.sourceforge.net \
--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