From: Tvrtko Ursulin <tursulin@igalia.com>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org, kernel-dev@igalia.com,
Tvrtko Ursulin <tvrtko.ursulin@igalia.com>,
Huang Ying <ying.huang@intel.com>,
Hugh Dickins <hughd@google.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/3] One fix for /proc/<pid>/numa_maps and two RFCs
Date: Fri, 5 Jul 2024 15:32:15 +0100 [thread overview]
Message-ID: <20240705143218.21258-1-tursulin@igalia.com> (raw)
From: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
Hi all,
First patch fixes the issue where NUMA balancing mode was wrongly shown
'default' and is small and so hopefully backportable to stable.c
Second two patches are more like RFC. Although they work I am not 100% sure of
their benefit. Especially the last patch which enables turning on NUMA balancing
with tmpfs. Second one at least makes the flag handling a bit more robust in the
sense that it can prevent future mistakes.
Comments and opinions are welcome!
Cc: Huang Ying <ying.huang@intel.com>
Cc: Hugh Dickins <hughd@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Tvrtko Ursulin (3):
mm/numa_balancing: Teach mpol_to_str about the balancing mode
mm/mempolicy: Use flags lookup array in mpol_to_str
mm/numa_balancing: Allow setting numa balancing for tmpfs
mm/mempolicy.c | 123 ++++++++++++++++++++++++++++++++++++-------------
1 file changed, 92 insertions(+), 31 deletions(-)
--
2.44.0
next reply other threads:[~2024-07-05 14:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 14:32 Tvrtko Ursulin [this message]
2024-07-05 14:32 ` [PATCH 1/3] mm/numa_balancing: Teach mpol_to_str about the balancing mode Tvrtko Ursulin
2024-07-05 14:43 ` Matthew Wilcox
2024-07-08 2:08 ` Huang, Ying
2024-07-05 14:32 ` [PATCH 2/3] mm/mempolicy: Use flags lookup array in mpol_to_str Tvrtko Ursulin
2024-07-05 14:32 ` [PATCH 3/3] mm/numa_balancing: Allow setting numa balancing for tmpfs Tvrtko Ursulin
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=20240705143218.21258-1-tursulin@igalia.com \
--to=tursulin@igalia.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=kernel-dev@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tvrtko.ursulin@igalia.com \
--cc=ying.huang@intel.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