From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Mel Gorman <mel@csn.ul.ie>
Cc: kosaki.motohiro@jp.fujitsu.com, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: mmotm 2009-09-03-16-35 uploaded
Date: Thu, 10 Sep 2009 09:02:59 +0900 (JST) [thread overview]
Message-ID: <20090910090141.9CC0.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <20090909093144.GD24614@csn.ul.ie>
> /me slaps self
>
> I think I see the problem. Can you try this patch please?
After the patch apply, the system boot successful.
Thanks, Mel!
Andrew, Could you please pick this patch?
> ---
> Calculate the number of pageblocks within a range properly
>
> Patch
> page-allocator-change-migratetype-for-all-pageblocks-within-a-high-order-page-during-__rmqueue_fallback
> is meant to change the pageblock ownership of each pageblock within a
> given range. This is necessary when the buddy to be split is of higher
> order than the pageblock_order. However, the calculation was wrong
> leading to crashes on ia-64 and slightly incorrect behaviour on x86.
> This patch corrects the calculation.
>
> Signed-off-by: Mel Gorman <mel@csn.ul.ie>
> ---
> mm/page_alloc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 4e0ec94..4326280 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -830,7 +830,7 @@ static int move_freepages_block(struct zone *zone, struct page *page,
> static void change_pageblock_range(struct page *pageblock_page,
> int start_order, int migratetype)
> {
> - int nr_pageblocks = 1 << (MAX_ORDER - 1 - start_order);
> + int nr_pageblocks = 1 << (start_order - pageblock_order);
>
> while (nr_pageblocks--) {
> set_pageblock_migratetype(pageblock_page, migratetype);
prev parent reply other threads:[~2009-09-10 0:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 23:40 akpm
2009-09-04 12:56 ` Dave Young
2009-09-04 23:17 ` Andrew Morton
2009-09-04 20:54 ` mount.nfs oops [was: mmotm 2009-09-03-16-35 uploaded] Jiri Slaby
2009-09-04 22:12 ` Trond Myklebust
2009-09-04 22:26 ` Jiri Slaby
2009-09-04 22:53 ` Trond Myklebust
2009-09-06 16:11 ` Jiri Slaby
2009-09-04 23:30 ` mmotm 2009-09-03-16-35 uploaded Randy Dunlap
2009-09-09 0:49 ` KOSAKI Motohiro
2009-09-09 1:14 ` KAMEZAWA Hiroyuki
2009-09-09 1:31 ` KAMEZAWA Hiroyuki
2009-09-10 1:39 ` KOSAKI Motohiro
2009-09-10 2:58 ` [PATCH][mmotm][BUGFIX] kcore use registered physmem information ia64-fix (Was " KAMEZAWA Hiroyuki
2009-09-11 1:25 ` KOSAKI Motohiro
2009-09-09 1:34 ` KOSAKI Motohiro
2009-09-09 7:35 ` Mel Gorman
2009-09-09 8:17 ` KOSAKI Motohiro
2009-09-09 8:47 ` Mel Gorman
2009-09-09 8:51 ` KOSAKI Motohiro
2009-09-09 9:31 ` Mel Gorman
2009-09-10 0:02 ` KOSAKI Motohiro [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=20090910090141.9CC0.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®