From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Michael Bohan <mbohan@codeaurora.org>
Cc: Mel Gorman <mel@csn.ul.ie>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: Kernel panic due to page migration accessing memory holes
Date: Fri, 19 Feb 2010 15:10:12 +0900 [thread overview]
Message-ID: <20100219151012.d430b7ea.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <4B7E2635.8010700@codeaurora.org>
On Thu, 18 Feb 2010 21:48:37 -0800
Michael Bohan <mbohan@codeaurora.org> wrote:
> On 2/18/2010 6:00 PM, KAMEZAWA Hiroyuki wrote:
> > memmap for memory holes should be marked as PG_reserved and never be freed
> > by free_bootmem(). Then, memmap for memory holes will not be in buddy allocator.
> >
> > Again, pfn_valid() just show "there is memmap", not for "there is a valid page"
> >
>
> ARM seems to have been freeing the memmap holes for a long time.
Ouch.
> I'm pretty sure there would be a lot of pushback if we tried to change
> that. For example, in my memory map running FLATMEM, I would be
> consuming an extra ~7 MB of memory if these structures were not freed.
>
> As a compromise, perhaps we could free everything except the first
> 'pageblock_nr_pages' in a hole? This would guarantee that
> move_freepages() doesn't deference any memory that doesn't belong to the
> memmap -- but still only waste a relatively small amount of memory. For
> a 4 MB page block, it should only consume an extra 32 KB per hole in the
> memory map.
>
No. You have to implement pfn_valid() to return correct value as
"pfn_valid() returnes true if there is memmap." even if you do that.
Otherwise, many things will go bad.
You have 2 or 3 ways.
1. re-implement pfn_valid() which returns correct value.
maybe not difficult. but please take care of defining CONFIG_HOLES_IN_....
etc.
2. use DISCONTIGMEM and treat each bank and NUMA node.
There will be no waste for memmap. But other complication of CONFIG_NUMA.
3. use SPARSEMEM.
You have even 2 choisce here.
a - Set your MAX_ORDER and SECTION_SIZE to be proper value.
b - waste some amount of memory for memmap on the edge of section.
(and don't free memmap for the edge.)
Thanks,
-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:[~2010-02-19 6:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 0:45 Michael Bohan
2010-02-18 1:03 ` KAMEZAWA Hiroyuki
2010-02-18 8:22 ` Michael Bohan
2010-02-18 9:36 ` KAMEZAWA Hiroyuki
2010-02-18 10:04 ` Mel Gorman
2010-02-19 1:47 ` Michael Bohan
2010-02-19 2:00 ` KAMEZAWA Hiroyuki
2010-02-19 5:48 ` Michael Bohan
2010-02-19 6:10 ` KAMEZAWA Hiroyuki [this message]
2010-02-19 8:21 ` KAMEZAWA Hiroyuki
2010-02-19 8:30 ` Russell King - ARM Linux
2010-02-19 13:48 ` Mel Gorman
2010-02-18 8:53 ` Russell King - ARM Linux
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=20100219151012.d430b7ea.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbohan@codeaurora.org \
--cc=mel@csn.ul.ie \
/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