From: Vlastimil Babka <vbabka@suse.cz>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org, Michal Hocko <mhocko@kernel.org>,
Pavel Tatashin <pasha.tatashin@soleen.com>,
David Hildenbrand <david@redhat.com>,
Oscar Salvador <osalvador@suse.de>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Vlastimil Babka <vbabka@suse.cz>
Subject: [RFC 0/5] disable pcplists during page isolation
Date: Mon, 7 Sep 2020 18:36:23 +0200 [thread overview]
Message-ID: <20200907163628.26495-1-vbabka@suse.cz> (raw)
As per the discussions [1] [2] this is an attempt to implement David's
suggestion that page isolation should disable pcplists to avoid races. This is
done without extra checks in fast paths, as I mentioned should be possible in
the discussion, and explained in patch 5. Patches 1-4 are preparatory cleanups.
Note this is untested RFC for now. Based on v5.9-rc4 plus Pavel's patch [2]
(slated as a quick fix for mainline+stable).
[1] https://lore.kernel.org/linux-mm/20200901124615.137200-1-pasha.tatashin@soleen.com/
[2] https://lore.kernel.org/linux-mm/20200903140032.380431-1-pasha.tatashin@soleen.com/
Vlastimil Babka (5):
mm, page_alloc: clean up pageset high and batch update
mm, page_alloc: calculate pageset high and batch once per zone
mm, page_alloc(): remove setup_pageset()
mm, page_alloc: cache pageset high and batch in struct zone
mm, page_alloc: disable pcplists during page isolation
include/linux/gfp.h | 1 +
include/linux/mmzone.h | 2 +
mm/internal.h | 4 ++
mm/memory_hotplug.c | 24 +++----
mm/page_alloc.c | 138 ++++++++++++++++++++++-------------------
mm/page_isolation.c | 45 +++++++++++---
6 files changed, 127 insertions(+), 87 deletions(-)
--
2.28.0
next reply other threads:[~2020-09-07 16:36 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 16:36 Vlastimil Babka [this message]
2020-09-07 16:36 ` [RFC 1/5] mm, page_alloc: clean up pageset high and batch update Vlastimil Babka
2020-09-10 8:31 ` Oscar Salvador
2020-09-10 8:34 ` Oscar Salvador
2020-09-10 10:47 ` David Hildenbrand
2020-09-17 16:05 ` Vlastimil Babka
2020-09-07 16:36 ` [RFC 2/5] mm, page_alloc: calculate pageset high and batch once per zone Vlastimil Babka
2020-09-10 9:00 ` Oscar Salvador
2020-09-10 10:56 ` David Hildenbrand
2020-09-07 16:36 ` [RFC 3/5] mm, page_alloc(): remove setup_pageset() Vlastimil Babka
2020-09-10 9:23 ` Oscar Salvador
2020-09-10 9:57 ` Oscar Salvador
2020-09-18 9:37 ` Vlastimil Babka
2020-09-10 11:00 ` David Hildenbrand
2020-09-07 16:36 ` [RFC 4/5] mm, page_alloc: cache pageset high and batch in struct zone Vlastimil Babka
2020-09-10 11:30 ` Oscar Salvador
2020-09-18 12:02 ` Vlastimil Babka
2020-09-07 16:36 ` [RFC 5/5] mm, page_alloc: disable pcplists during page isolation Vlastimil Babka
2020-09-09 10:48 ` Vlastimil Babka
2020-09-09 11:36 ` Michal Hocko
2020-09-09 11:44 ` David Hildenbrand
2020-09-09 12:57 ` David Hildenbrand
2020-09-09 11:55 ` Vlastimil Babka
2020-09-10 10:29 ` David Hildenbrand
2020-09-10 11:05 ` Vlastimil Babka
2020-09-10 12:42 ` David Hildenbrand
2020-09-09 12:53 ` Pavel Tatashin
2020-09-08 18:29 ` [RFC 0/5] " David Hildenbrand
2020-09-09 10:54 ` Vlastimil Babka
2020-09-09 11:27 ` osalvador
2020-09-09 11:29 ` 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=20200907163628.26495-1-vbabka@suse.cz \
--to=vbabka@suse.cz \
--cc=david@redhat.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=osalvador@suse.de \
--cc=pasha.tatashin@soleen.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 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).