From: Michal Hocko <mhocko@kernel.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Mel Gorman <mgorman@suse.de>, Joonsoo Kim <js1304@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] mm, compaction: allow compaction for GFP_NOFS requests
Date: Fri, 7 Oct 2016 08:50:19 +0200 [thread overview]
Message-ID: <20161007065019.GA18439@dhcp22.suse.cz> (raw)
In-Reply-To: <e7dc1e23-10fe-99de-e9c8-581857e3ab9d@suse.cz>
On Fri 07-10-16 07:27:37, Vlastimil Babka wrote:
[...]
> > diff --git a/mm/compaction.c b/mm/compaction.c
> > index badb92bf14b4..07254a73ee32 100644
> > --- a/mm/compaction.c
> > +++ b/mm/compaction.c
> > @@ -834,6 +834,13 @@ isolate_migratepages_block(struct compact_control *cc, unsigned long low_pfn,
> > page_count(page) > page_mapcount(page))
> > goto isolate_fail;
> >
> > + /*
> > + * Only allow to migrate anonymous pages in GFP_NOFS context
> > + * because those do not depend on fs locks.
> > + */
> > + if (!(cc->gfp_mask & __GFP_FS) && page_mapping(page))
> > + goto isolate_fail;
>
> Unless page can acquire a page_mapping between this check and migration, I
> don't see a problem with allowing this.
It can be become swapcache but I guess this should be OK. We do not
allow to get here with GFP_NOIO and migrating swapcache pages in NOFS
mode should be OK AFAICS.
> But make sure you don't break kcompactd and manual compaction from /proc, as
> they don't currently set cc->gfp_mask. Looks like until now it was only used
> to determine direct compactor's migratetype which is irrelevant in those
> contexts.
OK, I see. This is really subtle. One way to go would be to provide a
fake gfp_mask for them. How does the following look to you?
---
diff --git a/mm/compaction.c b/mm/compaction.c
index 557c165b63ad..d1d90e96ef4b 100644
--- a/mm/compaction.c
+++ b/mm/compaction.c
@@ -1779,6 +1779,7 @@ static void compact_node(int nid)
.mode = MIGRATE_SYNC,
.ignore_skip_hint = true,
.whole_zone = true,
+ .gfp_mask = GFP_KERNEL,
};
@@ -1904,6 +1905,7 @@ static void kcompactd_do_work(pg_data_t *pgdat)
.classzone_idx = pgdat->kcompactd_classzone_idx,
.mode = MIGRATE_SYNC_LIGHT,
.ignore_skip_hint = true,
+ .gfp_mask = GFP_KERNEL,
};
trace_mm_compaction_kcompactd_wake(pgdat->node_id, cc.order,
--
Michal Hocko
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: Michal Hocko <mhocko@kernel.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Mel Gorman <mgorman@suse.de>, Joonsoo Kim <js1304@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] mm, compaction: allow compaction for GFP_NOFS requests
Date: Fri, 7 Oct 2016 08:50:19 +0200 [thread overview]
Message-ID: <20161007065019.GA18439@dhcp22.suse.cz> (raw)
In-Reply-To: <e7dc1e23-10fe-99de-e9c8-581857e3ab9d@suse.cz>
On Fri 07-10-16 07:27:37, Vlastimil Babka wrote:
[...]
> > diff --git a/mm/compaction.c b/mm/compaction.c
> > index badb92bf14b4..07254a73ee32 100644
> > --- a/mm/compaction.c
> > +++ b/mm/compaction.c
> > @@ -834,6 +834,13 @@ isolate_migratepages_block(struct compact_control *cc, unsigned long low_pfn,
> > page_count(page) > page_mapcount(page))
> > goto isolate_fail;
> >
> > + /*
> > + * Only allow to migrate anonymous pages in GFP_NOFS context
> > + * because those do not depend on fs locks.
> > + */
> > + if (!(cc->gfp_mask & __GFP_FS) && page_mapping(page))
> > + goto isolate_fail;
>
> Unless page can acquire a page_mapping between this check and migration, I
> don't see a problem with allowing this.
It can be become swapcache but I guess this should be OK. We do not
allow to get here with GFP_NOIO and migrating swapcache pages in NOFS
mode should be OK AFAICS.
> But make sure you don't break kcompactd and manual compaction from /proc, as
> they don't currently set cc->gfp_mask. Looks like until now it was only used
> to determine direct compactor's migratetype which is irrelevant in those
> contexts.
OK, I see. This is really subtle. One way to go would be to provide a
fake gfp_mask for them. How does the following look to you?
---
diff --git a/mm/compaction.c b/mm/compaction.c
index 557c165b63ad..d1d90e96ef4b 100644
--- a/mm/compaction.c
+++ b/mm/compaction.c
@@ -1779,6 +1779,7 @@ static void compact_node(int nid)
.mode = MIGRATE_SYNC,
.ignore_skip_hint = true,
.whole_zone = true,
+ .gfp_mask = GFP_KERNEL,
};
@@ -1904,6 +1905,7 @@ static void kcompactd_do_work(pg_data_t *pgdat)
.classzone_idx = pgdat->kcompactd_classzone_idx,
.mode = MIGRATE_SYNC_LIGHT,
.ignore_skip_hint = true,
+ .gfp_mask = GFP_KERNEL,
};
trace_mm_compaction_kcompactd_wake(pgdat->node_id, cc.order,
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2016-10-07 6:50 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 8:12 [RFC PATCH] mm, compaction: allow compaction for GFP_NOFS requests Michal Hocko
2016-10-04 8:12 ` Michal Hocko
2016-10-04 20:32 ` Dave Chinner
2016-10-04 20:32 ` Dave Chinner
2016-10-05 11:38 ` Michal Hocko
2016-10-05 11:38 ` Michal Hocko
2016-10-06 2:11 ` Dave Chinner
2016-10-06 2:11 ` Dave Chinner
2016-10-07 13:18 ` Michal Hocko
2016-10-07 13:18 ` Michal Hocko
2016-10-13 0:29 ` Dave Chinner
2016-10-13 0:29 ` Dave Chinner
2016-10-13 7:39 ` Michal Hocko
2016-10-13 7:39 ` Michal Hocko
2016-10-13 11:04 ` Michal Hocko
2016-10-13 11:04 ` Michal Hocko
2016-10-16 20:49 ` Dave Chinner
2016-10-16 20:49 ` Dave Chinner
2016-10-17 8:22 ` Michal Hocko
2016-10-17 8:22 ` Michal Hocko
2016-10-18 6:24 ` Dave Chinner
2016-10-18 6:24 ` Dave Chinner
2016-10-18 12:29 ` Michal Hocko
2016-10-18 12:29 ` Michal Hocko
2016-10-07 5:27 ` Vlastimil Babka
2016-10-07 5:27 ` Vlastimil Babka
2016-10-07 6:50 ` Michal Hocko [this message]
2016-10-07 6:50 ` Michal Hocko
2016-10-07 8:15 ` Vlastimil Babka
2016-10-07 8:15 ` Vlastimil Babka
2016-10-07 9:21 ` Michal Hocko
2016-10-07 9:21 ` Michal Hocko
2016-10-10 6:44 ` Vlastimil Babka
2016-10-10 6:44 ` Vlastimil Babka
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=20161007065019.GA18439@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=js1304@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--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 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.