From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: Mel Gorman <mel@csn.ul.ie>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, apw@shadowen.org,
kamezawa.hiroyu@jp.fujitsu.com
Subject: Re: [PATCH 2/2] Align ZONE_MOVABLE to a MAX_ORDER_NR_PAGES boundary
Date: Wed, 25 Apr 2007 11:00:58 +0900 [thread overview]
Message-ID: <20070425105604.FBB4.Y-GOTO@jp.fujitsu.com> (raw)
In-Reply-To: <20070424180112.22005.34624.sendpatchset@skynet.skynet.ie>
Looks good. :-)
Thanks.
Acked-by: Yasunori Goto <y-goto@jp.fujitsu.com>
>
> The boot memory allocator makes assumptions on the alignment of zone
> boundaries even though the buddy allocator has no requirements on the
> alignment of zones. This may cause boot problems in situations where
> ZONE_MOVABLE is populated because the bootmem allocator assumes zones are
> at least order-log2(BITS_PER_LONG) aligned. As the two potential users
> (huge pages and memory hot-remove) of ZONE_MOVABLE would prefer a higher
> alignment, this patch aligns the start of the zone instead of fixing the
> different assumptions made by the bootmem allocator.
>
> This patch rounds the start of ZONE_MOVABLE in each node to a
> MAX_ORDER_NR_PAGES boundary. If the rounding pushes the start of ZONE_MOVABLE
> above the end of the node then the zone will contain no memory and will not
> be used at runtime. The value is rounded up instead of down as it is
> better to have the kernel-portion of memory larger than requested instead
> of smaller. The impact is that the kernel-usable portion of memory because a
> minimum guarantee instead of the exact size requested by the user.
>
>
> Signed-off-by: Mel Gorman <mel@csn.ul.ie>
> Acked-by: Andy Whitcroft <apw@shadowen.org>
> ---
>
> page_alloc.c | 5 +++++
> 1 files changed, 5 insertions(+)
>
> diff -rup -X /usr/src/patchset-0.6/bin//dontdiff linux-2.6.21-rc6-mm1-002_commonparse/mm/page_alloc.c linux-2.6.21-rc6-mm1-003_alignmovable/mm/page_alloc.c
> --- linux-2.6.21-rc6-mm1-002_commonparse/mm/page_alloc.c 2007-04-24 09:38:30.000000000 +0100
> +++ linux-2.6.21-rc6-mm1-003_alignmovable/mm/page_alloc.c 2007-04-24 11:15:40.000000000 +0100
> @@ -3642,6 +3642,11 @@ restart:
> usable_nodes--;
> if (usable_nodes && required_kernelcore > usable_nodes)
> goto restart;
> +
> + /* Align start of ZONE_MOVABLE on all nids to MAX_ORDER_NR_PAGES */
> + for (nid = 0; nid < MAX_NUMNODES; nid++)
> + zone_movable_pfn[nid] =
> + roundup(zone_movable_pfn[nid], MAX_ORDER_NR_PAGES);
> }
>
> /**
--
Yasunori Goto
--
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>
prev parent reply other threads:[~2007-04-25 2:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-24 18:00 [PATCH 0/2] Fix two boot problems related to ZONE_MOVABLE sizing Mel Gorman
2007-04-24 18:00 ` [PATCH 1/2] Handle kernelcore= boot parameter in common code to avoid boot problem on IA64 Mel Gorman
2007-04-24 21:04 ` Andrew Morton
2007-04-24 18:01 ` [PATCH 2/2] Align ZONE_MOVABLE to a MAX_ORDER_NR_PAGES boundary Mel Gorman
2007-04-25 2:00 ` Yasunori Goto [this message]
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=20070425105604.FBB4.Y-GOTO@jp.fujitsu.com \
--to=y-goto@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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