From: Mel Gorman <mgorman@suse.de>
To: Laura Abbott <lauraa@codeaurora.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v3] mm: Use aligned zone start for pfn_to_bitidx calculation
Date: Thu, 13 Dec 2012 11:20:58 +0000 [thread overview]
Message-ID: <20121213112058.GA9887@suse.de> (raw)
In-Reply-To: <1354828301-27849-1-git-send-email-lauraa@codeaurora.org>
On Thu, Dec 06, 2012 at 01:11:41PM -0800, Laura Abbott wrote:
> The current calculation in pfn_to_bitidx assumes that
> (pfn - zone->zone_start_pfn) >> pageblock_order will return the
> same bit for all pfn in a pageblock. If zone_start_pfn is not
> aligned to pageblock_nr_pages, this may not always be correct.
>
> Consider the following with pageblock order = 10, zone start 2MB:
>
> pfn | pfn - zone start | (pfn - zone start) >> page block order
> ----------------------------------------------------------------
> 0x26000 | 0x25e00 | 0x97
> 0x26100 | 0x25f00 | 0x97
> 0x26200 | 0x26000 | 0x98
> 0x26300 | 0x26100 | 0x98
>
> This means that calling {get,set}_pageblock_migratetype on a single
> page will not set the migratetype for the full block. Fix this by
> rounding down zone_start_pfn when doing the bitidx calculation.
>
> Signed-off-by: Laura Abbott <lauraa@codeaurora.org>
Acked-by: Mel Gorman <mgorman@suse.de>
It's merge window at the moment so it's in danger of getting lost. What
I suggest you do is do is resend to Andrew with the same people cc'd
post-merge window so it'll be picked up in mmotm for the next cycle.
Thanks.
--
Mel Gorman
SUSE Labs
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Mel Gorman <mgorman@suse.de>
To: Laura Abbott <lauraa@codeaurora.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v3] mm: Use aligned zone start for pfn_to_bitidx calculation
Date: Thu, 13 Dec 2012 11:20:58 +0000 [thread overview]
Message-ID: <20121213112058.GA9887@suse.de> (raw)
In-Reply-To: <1354828301-27849-1-git-send-email-lauraa@codeaurora.org>
On Thu, Dec 06, 2012 at 01:11:41PM -0800, Laura Abbott wrote:
> The current calculation in pfn_to_bitidx assumes that
> (pfn - zone->zone_start_pfn) >> pageblock_order will return the
> same bit for all pfn in a pageblock. If zone_start_pfn is not
> aligned to pageblock_nr_pages, this may not always be correct.
>
> Consider the following with pageblock order = 10, zone start 2MB:
>
> pfn | pfn - zone start | (pfn - zone start) >> page block order
> ----------------------------------------------------------------
> 0x26000 | 0x25e00 | 0x97
> 0x26100 | 0x25f00 | 0x97
> 0x26200 | 0x26000 | 0x98
> 0x26300 | 0x26100 | 0x98
>
> This means that calling {get,set}_pageblock_migratetype on a single
> page will not set the migratetype for the full block. Fix this by
> rounding down zone_start_pfn when doing the bitidx calculation.
>
> Signed-off-by: Laura Abbott <lauraa@codeaurora.org>
Acked-by: Mel Gorman <mgorman@suse.de>
It's merge window at the moment so it's in danger of getting lost. What
I suggest you do is do is resend to Andrew with the same people cc'd
post-merge window so it'll be picked up in mmotm for the next cycle.
Thanks.
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2012-12-13 11:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 21:11 [PATCH v3] mm: Use aligned zone start for pfn_to_bitidx calculation Laura Abbott
2012-12-06 21:11 ` Laura Abbott
2012-12-13 11:20 ` Mel Gorman [this message]
2012-12-13 11:20 ` 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=20121213112058.GA9887@suse.de \
--to=mgorman@suse.de \
--cc=lauraa@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.