From: Pavel Tatashin <pasha.tatashin@soleen.com>
To: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
mhocko@suse.com, linux-mm@kvack.org, pasha.tatashin@soleen.com,
osalvador@suse.de, richard.weiyang@gmail.com, david@redhat.com,
vbabka@suse.cz, rientjes@google.com
Subject: [PATCH v3 0/2] drain pcp outside of page isolation
Date: Fri, 4 Sep 2020 11:14:46 -0400 [thread overview]
Message-ID: <20200904151448.100489-1-pasha.tatashin@soleen.com> (raw)
Moved drain_all_pages() from start_isolate_page_range() to users. This
makes it more efficient, symmetric, and solves the race condition.
This is a proposal that I described in Version 1 thread, otherwise no changes
to patch 1.
Version 1:
https://lore.kernel.org/lkml/20200901124615.137200-1-pasha.tatashin@soleen.com
Version 2:
https://lore.kernel.org/lkml/20200903140032.380431-1-pasha.tatashin@soleen.com
Pavel Tatashin (2):
mm/memory_hotplug: drain per-cpu pages again during memory offline
mm: drain per-cpu pages outside of isolate_migratepages_range
mm/memory_hotplug.c | 1 +
mm/page_alloc.c | 2 ++
mm/page_isolation.c | 32 ++++++++++++--------------------
3 files changed, 15 insertions(+), 20 deletions(-)
--
2.25.1
next reply other threads:[~2020-09-04 15:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 15:14 Pavel Tatashin [this message]
2020-09-04 15:14 ` [PATCH v3 1/2] mm/memory_hotplug: drain per-cpu pages again during memory offline Pavel Tatashin
2020-09-07 7:27 ` Michal Hocko
2020-09-08 9:57 ` David Hildenbrand
2020-09-04 15:14 ` [PATCH v3 2/2] mm: drain per-cpu pages outside of isolate_migratepages_range Pavel Tatashin
2020-09-07 7:32 ` Michal Hocko
2020-09-08 9:26 ` David Hildenbrand
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=20200904151448.100489-1-pasha.tatashin@soleen.com \
--to=pasha.tatashin@soleen.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=osalvador@suse.de \
--cc=richard.weiyang@gmail.com \
--cc=rientjes@google.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).