From: Vlastimil Babka <vbabka@suse.cz>
To: Weijie Yang <weijie.yang@samsung.com>, iamjoonsoo.kim@lge.com
Cc: 'Andrew Morton' <akpm@linux-foundation.org>,
mgorman@suse.de, 'Rik van Riel' <riel@redhat.com>,
'Johannes Weiner' <hannes@cmpxchg.org>,
'Minchan Kim' <minchan@kernel.org>,
'Weijie Yang' <weijie.yang.kh@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 2/3] mm: page_isolation: remove unnecessary freepage_migratetype check for unused page
Date: Tue, 09 Dec 2014 10:24:27 +0100 [thread overview]
Message-ID: <5486BFCB.4040305@suse.cz> (raw)
In-Reply-To: <000201d01385$25a6c950$70f45bf0$%yang@samsung.com>
On 12/09/2014 08:51 AM, Weijie Yang wrote:
> when we test the pages in a range is free or not, there is a little
> chance we encounter some page which is not in buddy but page_count is 0.
> That means that page could be in the page-freeing path but not in the
> buddy freelist, such as in pcplist
This shouldn't happen anymore IMHO. The pageblock is marked as
MIGRATE_ISOLATE and then a lru+pcplist drain is performed. Nothing
should be left on pcplist - anything newly freed goes directly to free
lists. Hm, maybe it could be on lru cache, but that holds a page
reference IIRC, so this test won't pass.
> or wait for the zone->lock which the
> tester is holding.
That could maybe happen, but is it worth testing? If yes, please add it
in a comment to the code.
> Back to the freepage_migratetype, we use it for a cached value for decide
> which free-list the page go when freeing page. If the pageblock is isolated
> the page will go to free-list[MIGRATE_ISOLATE] even if the cached type is
> not MIGRATE_ISOLATE, the commit ad53f92e(fix incorrect isolation behavior
> by rechecking migratetype) patch series have ensure this.
>
> So the freepage_migratetype check for page_count==0 page in
> __test_page_isolated_in_pageblock() is meaningless.
> This patch removes the unnecessary freepage_migratetype check.
>
> Signed-off-by: Weijie Yang <weijie.yang@samsung.com>
> ---
> mm/page_isolation.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/mm/page_isolation.c b/mm/page_isolation.c
> index 6e5174d..f7c9183 100644
> --- a/mm/page_isolation.c
> +++ b/mm/page_isolation.c
> @@ -223,8 +223,7 @@ __test_page_isolated_in_pageblock(unsigned long pfn, unsigned long end_pfn,
> page = pfn_to_page(pfn);
> if (PageBuddy(page))
> pfn += 1 << page_order(page);
> - else if (page_count(page) == 0 &&
> - get_freepage_migratetype(page) == MIGRATE_ISOLATE)
> + else if (page_count(page) == 0)
> pfn += 1;
> else if (skip_hwpoisoned_pages && PageHWPoison(page)) {
> /*
>
--
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: Vlastimil Babka <vbabka@suse.cz>
To: Weijie Yang <weijie.yang@samsung.com>, iamjoonsoo.kim@lge.com
Cc: "'Andrew Morton'" <akpm@linux-foundation.org>,
mgorman@suse.de, "'Rik van Riel'" <riel@redhat.com>,
"'Johannes Weiner'" <hannes@cmpxchg.org>,
"'Minchan Kim'" <minchan@kernel.org>,
"'Weijie Yang'" <weijie.yang.kh@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 2/3] mm: page_isolation: remove unnecessary freepage_migratetype check for unused page
Date: Tue, 09 Dec 2014 10:24:27 +0100 [thread overview]
Message-ID: <5486BFCB.4040305@suse.cz> (raw)
In-Reply-To: <000201d01385$25a6c950$70f45bf0$%yang@samsung.com>
On 12/09/2014 08:51 AM, Weijie Yang wrote:
> when we test the pages in a range is free or not, there is a little
> chance we encounter some page which is not in buddy but page_count is 0.
> That means that page could be in the page-freeing path but not in the
> buddy freelist, such as in pcplist
This shouldn't happen anymore IMHO. The pageblock is marked as
MIGRATE_ISOLATE and then a lru+pcplist drain is performed. Nothing
should be left on pcplist - anything newly freed goes directly to free
lists. Hm, maybe it could be on lru cache, but that holds a page
reference IIRC, so this test won't pass.
> or wait for the zone->lock which the
> tester is holding.
That could maybe happen, but is it worth testing? If yes, please add it
in a comment to the code.
> Back to the freepage_migratetype, we use it for a cached value for decide
> which free-list the page go when freeing page. If the pageblock is isolated
> the page will go to free-list[MIGRATE_ISOLATE] even if the cached type is
> not MIGRATE_ISOLATE, the commit ad53f92e(fix incorrect isolation behavior
> by rechecking migratetype) patch series have ensure this.
>
> So the freepage_migratetype check for page_count==0 page in
> __test_page_isolated_in_pageblock() is meaningless.
> This patch removes the unnecessary freepage_migratetype check.
>
> Signed-off-by: Weijie Yang <weijie.yang@samsung.com>
> ---
> mm/page_isolation.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/mm/page_isolation.c b/mm/page_isolation.c
> index 6e5174d..f7c9183 100644
> --- a/mm/page_isolation.c
> +++ b/mm/page_isolation.c
> @@ -223,8 +223,7 @@ __test_page_isolated_in_pageblock(unsigned long pfn, unsigned long end_pfn,
> page = pfn_to_page(pfn);
> if (PageBuddy(page))
> pfn += 1 << page_order(page);
> - else if (page_count(page) == 0 &&
> - get_freepage_migratetype(page) == MIGRATE_ISOLATE)
> + else if (page_count(page) == 0)
> pfn += 1;
> else if (skip_hwpoisoned_pages && PageHWPoison(page)) {
> /*
>
next prev parent reply other threads:[~2014-12-09 9:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 7:51 [PATCH 2/3] mm: page_isolation: remove unnecessary freepage_migratetype check for unused page Weijie Yang
2014-12-09 7:51 ` Weijie Yang
2014-12-09 9:24 ` Vlastimil Babka [this message]
2014-12-09 9:24 ` Vlastimil Babka
2014-12-10 14:10 ` Weijie Yang
2014-12-10 14:10 ` Weijie Yang
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=5486BFCB.4040305@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=riel@redhat.com \
--cc=weijie.yang.kh@gmail.com \
--cc=weijie.yang@samsung.com \
/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.