From: Nico Pache <npache@redhat.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org
Cc: shakeelb@google.com, ktkhai@virtuozzo.com, shy828301@gmail.com,
guro@fb.com, vbabka@suse.cz, vdavydov.dev@gmail.com,
raquini@redhat.com, mhocko@suse.com, david@redhat.com
Subject: [PATCH v2 0/1] Dont allocate pages on a offline node
Date: Tue, 7 Dec 2021 17:40:12 -0500 [thread overview]
Message-ID: <20211207224013.880775-1-npache@redhat.com> (raw)
Prevent page allocations from occuring on an offlined by adding a check
to confirm the node is online and if not, use the closest node. Some
further work is needed for my previous solution to be complete. This
will provide a fix to the problem while the more complete solution is
being worked on.
V2:
* drop the first patch that will introduce a regression by adding a
branch in the hotpath.
* Remove the for_each_online_nodes introduced as that will require
further work for memcg and hotplug to work correctly. Long term a
rework will be needed to either allocate all pgdatas or update all
memcgs when a new node is onlined.
Signed-off-by: Nico Pache <npache@redhat.com>
Nico Pache (1):
mm/vmscan.c: Prevent allocating shrinker_info on offlined nodes
mm/vmscan.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
--
2.33.1
next reply other threads:[~2021-12-07 22:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 22:40 Nico Pache [this message]
2021-12-07 22:40 ` [PATCH v2 1/1] mm/vmscan.c: Prevent allocating shrinker_info on offlined nodes Nico Pache
2021-12-07 23:34 ` Matthew Wilcox
2021-12-08 0:25 ` Nico Pache
2021-12-08 1:53 ` Andrew Morton
2021-12-07 23:44 ` Andrew Morton
2021-12-08 0:26 ` Yang Shi
2021-12-08 0:33 ` Nico Pache
2021-12-08 1:23 ` Yang Shi
2021-12-08 1:26 ` Yang Shi
2021-12-08 7:59 ` Michal Hocko
2021-12-13 19:10 ` Yang Shi
2022-01-10 17:09 ` Rafael Aquini
2022-01-10 17:16 ` Michal Hocko
2022-01-10 17:21 ` Rafael Aquini
2021-12-08 0:40 ` Nico Pache
2021-12-08 7:54 ` 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=20211207224013.880775-1-npache@redhat.com \
--to=npache@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=guro@fb.com \
--cc=ktkhai@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=raquini@redhat.com \
--cc=shakeelb@google.com \
--cc=shy828301@gmail.com \
--cc=vbabka@suse.cz \
--cc=vdavydov.dev@gmail.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