From: Minchan Kim <minchan@kernel.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@techsingularity.net>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Sangseok Lee <sangseok.lee@lge.com>
Subject: Re: [PATCH 1/4] mm: adjust reserved highatomic count
Date: Fri, 7 Oct 2016 23:29:19 +0900 [thread overview]
Message-ID: <20161007142919.GA3060@bbox> (raw)
In-Reply-To: <7ac7c0d8-4b7b-e362-08e7-6d62ee20f4c3@suse.cz>
Hi Vlastimil,
On Fri, Oct 07, 2016 at 02:30:04PM +0200, Vlastimil Babka wrote:
> On 10/07/2016 07:45 AM, Minchan Kim wrote:
> >In page freeing path, migratetype is racy so that a highorderatomic
> >page could free into non-highorderatomic free list.
>
> Yes. If page from a pageblock went to a pcplist before that pageblock was
> reserved as highatomic, free_pcppages_bulk() will misplace it.
As well, high-order freeing path has a problem, too.
CPU 1 CPU 2
__free_pages_ok
/* got highatomic mt */
unreserve_highatomic_pageblock mt = get_pfnblock_migratetype
spin_lock_irqsave(&zone->lock);
move_freepages_block
/* change from highatomic to something
set_pageblock_migratetype(page)
spin_unlock_irqrestore(&zone->lock)
spin_lock(&zone->lock);
/* highatomic mt is stale */
__free_one_page(page, mt);
Acutually, I tried to solve this problem with fixing the free path
but it needs to add a branch to verify highorderatomic mt in
both order-0 and high-order page freeing path. On highorder page freeing
path wouldn't be a problem but I don't want to add the branch in pcp
freeing path which is hot.
>
> >If that page
> >is allocated, VM can change the pageblock from higorderatomic to
> >something.
>
> More specifically, steal_suitable_fallback(). Yes.
As well, __isolate_free_page, too.
>
> >In that case, we should adjust nr_reserved_highatomic.
> >Otherwise, VM cannot reserve highorderatomic pageblocks any more
> >although it doesn't reach 1% limit. It means highorder atomic
> >allocation failure would be higher.
> >
> >So, this patch decreases the account as well as migratetype
> >if it was MIGRATE_HIGHATOMIC.
> >
> >Signed-off-by: Minchan Kim <minchan@kernel.org>
>
> Hm wouldn't it be simpler just to prevent the pageblock's migratetype to be
> changed if it's highatomic? Possibly also not do move_freepages_block() in
It could be. Actually, I did it with modifying can_steal_fallback which returns
false it found the pageblock is highorderatomic but changed to this way again
because I don't have any justification to prevent changing pageblock.
If you give concrete justification so others isn't against on it, I am happy to
do what you suggested.
> that case. Most accurate would be to put such misplaced page on the proper
> freelist and retry the fallback, but that might be overkill.
>
> >---
> > mm/page_alloc.c | 44 ++++++++++++++++++++++++++++++++++++++------
> > 1 file changed, 38 insertions(+), 6 deletions(-)
> >
> >diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> >index 55ad0229ebf3..e7cbb3cc22fa 100644
> >--- a/mm/page_alloc.c
> >+++ b/mm/page_alloc.c
> >@@ -282,6 +282,9 @@ EXPORT_SYMBOL(nr_node_ids);
> > EXPORT_SYMBOL(nr_online_nodes);
> > #endif
> >
> >+static void dec_highatomic_pageblock(struct zone *zone, struct page *page,
> >+ int migratetype);
> >+
> > int page_group_by_mobility_disabled __read_mostly;
> >
> > #ifdef CONFIG_DEFERRED_STRUCT_PAGE_INIT
> >@@ -1935,7 +1938,14 @@ static void change_pageblock_range(struct page *pageblock_page,
> > int nr_pageblocks = 1 << (start_order - pageblock_order);
> >
> > while (nr_pageblocks--) {
> >- set_pageblock_migratetype(pageblock_page, migratetype);
> >+ if (get_pageblock_migratetype(pageblock_page) !=
> >+ MIGRATE_HIGHATOMIC)
> >+ set_pageblock_migratetype(pageblock_page,
> >+ migratetype);
> >+ else
> >+ dec_highatomic_pageblock(page_zone(pageblock_page),
> >+ pageblock_page,
> >+ migratetype);
> > pageblock_page += pageblock_nr_pages;
> > }
> > }
> >@@ -1996,8 +2006,14 @@ static void steal_suitable_fallback(struct zone *zone, struct page *page,
> >
> > /* Claim the whole block if over half of it is free */
> > if (pages >= (1 << (pageblock_order-1)) ||
> >- page_group_by_mobility_disabled)
> >- set_pageblock_migratetype(page, start_type);
> >+ page_group_by_mobility_disabled) {
> >+ int mt = get_pageblock_migratetype(page);
> >+
> >+ if (mt != MIGRATE_HIGHATOMIC)
> >+ set_pageblock_migratetype(page, start_type);
> >+ else
> >+ dec_highatomic_pageblock(zone, page, start_type);
> >+ }
> > }
> >
> > /*
> >@@ -2037,6 +2053,17 @@ int find_suitable_fallback(struct free_area *area, unsigned int order,
> > return -1;
> > }
> >
> >+static void dec_highatomic_pageblock(struct zone *zone, struct page *page,
> >+ int migratetype)
> >+{
> >+ if (zone->nr_reserved_highatomic <= pageblock_nr_pages)
> >+ return;
> >+
> >+ zone->nr_reserved_highatomic -= min(pageblock_nr_pages,
> >+ zone->nr_reserved_highatomic);
> >+ set_pageblock_migratetype(page, migratetype);
> >+}
> >+
> > /*
> > * Reserve a pageblock for exclusive use of high-order atomic allocations if
> > * there are no empty page blocks that contain a page with a suitable order
> >@@ -2555,9 +2582,14 @@ int __isolate_free_page(struct page *page, unsigned int order)
> > struct page *endpage = page + (1 << order) - 1;
> > for (; page < endpage; page += pageblock_nr_pages) {
> > int mt = get_pageblock_migratetype(page);
> >- if (!is_migrate_isolate(mt) && !is_migrate_cma(mt))
> >- set_pageblock_migratetype(page,
> >- MIGRATE_MOVABLE);
> >+ if (!is_migrate_isolate(mt) && !is_migrate_cma(mt)) {
> >+ if (mt != MIGRATE_HIGHATOMIC)
> >+ set_pageblock_migratetype(page,
> >+ MIGRATE_MOVABLE);
> >+ else
> >+ dec_highatomic_pageblock(zone, page,
> >+ MIGRATE_MOVABLE);
> >+ }
> > }
> > }
> >
> >
>
--
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:[~2016-10-07 14:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 5:45 [PATCH 0/4] use up highorder free pages before OOM Minchan Kim
2016-10-07 5:45 ` [PATCH 1/4] mm: adjust reserved highatomic count Minchan Kim
2016-10-07 12:30 ` Vlastimil Babka
2016-10-07 14:29 ` Minchan Kim [this message]
2016-10-10 6:57 ` Vlastimil Babka
2016-10-11 4:19 ` Minchan Kim
2016-10-11 9:40 ` Vlastimil Babka
2016-10-12 5:36 ` Mel Gorman
2016-10-07 5:45 ` [PATCH 2/4] mm: prevent double decrease of nr_reserved_highatomic Minchan Kim
2016-10-07 12:44 ` Vlastimil Babka
2016-10-07 14:30 ` Minchan Kim
2016-10-12 5:36 ` Mel Gorman
2016-10-07 5:45 ` [PATCH 3/4] mm: unreserve highatomic free pages fully before OOM Minchan Kim
2016-10-07 9:09 ` Michal Hocko
2016-10-07 14:43 ` Minchan Kim
2016-10-10 7:41 ` Michal Hocko
2016-10-11 5:01 ` Minchan Kim
2016-10-11 6:50 ` Michal Hocko
2016-10-11 7:09 ` Minchan Kim
2016-10-11 7:26 ` Michal Hocko
2016-10-11 7:37 ` Minchan Kim
2016-10-11 8:01 ` Michal Hocko
2016-10-07 5:45 ` [PATCH 4/4] mm: skip to reserve pageblock crossed zone boundary for HIGHATOMIC Minchan Kim
2016-10-07 9:16 ` [PATCH 0/4] use up highorder free pages before OOM Michal Hocko
2016-10-07 15:04 ` Minchan Kim
2016-10-10 7:47 ` Michal Hocko
2016-10-11 5:06 ` Minchan Kim
2016-10-11 6:53 ` Michal Hocko
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=20161007142919.GA3060@bbox \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=sangseok.lee@lge.com \
--cc=vbabka@suse.cz \
/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).