From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Mel Gorman <mel@csn.ul.ie>
Cc: Minchan Kim <minchan.kim@gmail.com>,
Yinghai Lu <yinghai@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
Shaohua Li <shaohua.li@intel.com>,
Yakui Zhao <yakui.zhao@intel.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
arm-kernel@lists.infradead.org, kgene.kim@samsung.com,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [RFC] Tight check of pfn_valid on sparsemem
Date: Tue, 13 Jul 2010 10:46:12 +0100 [thread overview]
Message-ID: <20100713094612.GF20590@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20100713093700.GD29885@csn.ul.ie>
On Tue, Jul 13, 2010 at 10:37:00AM +0100, Mel Gorman wrote:
> I prefer Kamezawa's suggestion of mapping on a ZERO_PAGE-like page full
> of PageReserved struct pages because it would have better performance
> and be more in line with maintaining the assumptions of the memory
> model. If we go in this direction, I would strongly prefer it was an
> ARM-only thing.
As I've said, this is not possible without doing some serious page
manipulation.
Plus the pages that where there become unusable as they don't correspond
with a PFN or obey phys_to_virt(). So there's absolutely no point to
this.
Now, why do we free the holes in the mem_map - because these holes can
be extremely large. Every 512K of hole equates to one page of mem_map
array. Balance that against memory placed at 0xc0000000 physical on
some platforms, and with PHYSMEM_BITS at 32 and SECTION_SIZE_BITS at
19 - well, you do the maths. The result is certainly not pretty.
--
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-07-13 9:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 15:53 [RFC] Tight check of pfn_valid on sparsemem Minchan Kim
2010-07-12 23:59 ` Kukjin Kim
2010-07-13 3:19 ` KAMEZAWA Hiroyuki
2010-07-13 4:11 ` Minchan Kim
2010-07-13 4:23 ` KAMEZAWA Hiroyuki
2010-07-13 6:04 ` Minchan Kim
2010-07-13 6:40 ` KAMEZAWA Hiroyuki
2010-07-13 8:06 ` Minchan Kim
2010-07-13 8:03 ` KAMEZAWA Hiroyuki
2010-07-13 7:20 ` Russell King - ARM Linux
2010-07-13 7:34 ` KAMEZAWA Hiroyuki
2010-07-13 7:58 ` KAMEZAWA Hiroyuki
2010-07-13 8:02 ` KAMEZAWA Hiroyuki
2010-07-13 18:39 ` Russell King - ARM Linux
2010-07-13 20:46 ` Dave Hansen
2010-07-13 9:30 ` Johannes Weiner
2010-07-13 15:43 ` Minchan Kim
2010-07-13 16:35 ` Dave Hansen
2010-07-13 16:44 ` Minchan Kim
2010-07-14 0:23 ` KAMEZAWA Hiroyuki
2010-07-14 6:44 ` Minchan Kim
2010-07-14 7:10 ` KAMEZAWA Hiroyuki
2010-07-14 7:35 ` Minchan Kim
2010-07-14 7:39 ` KAMEZAWA Hiroyuki
2010-07-14 7:50 ` Kukjin Kim
2010-07-14 8:09 ` KAMEZAWA Hiroyuki
2010-07-13 9:37 ` Mel Gorman
2010-07-13 9:46 ` Russell King - ARM Linux [this message]
2010-07-13 10:00 ` 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=20100713094612.GF20590@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=arm-kernel@lists.infradead.org \
--cc=hpa@zytor.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kgene.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=minchan.kim@gmail.com \
--cc=shaohua.li@intel.com \
--cc=yakui.zhao@intel.com \
--cc=yinghai@kernel.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;
as well as URLs for NNTP newsgroup(s).