From: Yafang Shao <laoar.shao@gmail.com>
To: akpm@linux-foundation.org, paul@paul-moore.com,
jmorris@namei.org, serge@hallyn.com, omosnace@redhat.com,
mhocko@suse.com, ying.huang@intel.com
Cc: linux-mm@kvack.org, linux-security-module@vger.kernel.org,
bpf@vger.kernel.org, ligang.bdlg@bytedance.com,
Yafang Shao <laoar.shao@gmail.com>,
Alejandro Colomar <alx.manpages@gmail.com>,
Michael Kerrisk <mtk.manpages@gmail.com>
Subject: [PATCH v3 7/7] NOT kernel/man2/mbind.2: Add mode flag MPOL_F_NUMA_BALANCING
Date: Fri, 1 Dec 2023 09:46:36 +0000 [thread overview]
Message-ID: <20231201094636.19770-8-laoar.shao@gmail.com> (raw)
In-Reply-To: <20231201094636.19770-1-laoar.shao@gmail.com>
In Linux Kernel 5.12, a new mode flag, MPOL_F_NUMA_BALANCING, was
added to set_mempolicy() to optimize the page placement among the
NUMA nodes with the NUMA balancing mechanism even if the memory of
the applications is bound with MPOL_BIND.
In Linux Kernel 5.15, this mode flag was extended to mbind(2). Let's
also add man-page for mbind(2). It is copied from set_mempoicy(2)
man-page with subtle modifications.
Related kernel commits:
bda420b985054a3badafef23807c4b4fa38a3dff
6d2aec9e123bb9c49cb5c7fc654f25f81e688e8c
Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
Cc: "Huang, Ying" <ying.huang@intel.com>
Cc: Alejandro Colomar <alx.manpages@gmail.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>
---
man2/mbind.2 | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/man2/mbind.2 b/man2/mbind.2
index ba1b81ae9..dac784389 100644
--- a/man2/mbind.2
+++ b/man2/mbind.2
@@ -142,6 +142,23 @@ The supported
.I "mode flags"
are:
.TP
+.BR MPOL_F_NUMA_BALANCING " (since Linux 5.15)"
+.\" commit bda420b985054a3badafef23807c4b4fa38a3dff
+.\" commit 6d2aec9e123bb9c49cb5c7fc654f25f81e688e8c
+When
+.I mode
+is
+.BR MPOL_BIND ,
+enable the kernel NUMA balancing for the task if it is supported by the kernel.
+If the flag isn't supported by the kernel, or is used with
+.I mode
+other than
+.BR MPOL_BIND ,
+\-1 is returned and
+.I errno
+is set to
+.BR EINVAL .
+.TP
.BR MPOL_F_STATIC_NODES " (since Linux-2.6.26)"
A nonempty
.I nodemask
--
2.39.3
prev parent reply other threads:[~2023-12-01 9:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 9:46 [PATCH v3 0/7] mm, security, bpf: Fine-grained control over memory policy adjustments with lsm bpf Yafang Shao
2023-12-01 9:46 ` [PATCH v3 1/7] mm, doc: Add doc for MPOL_F_NUMA_BALANCING Yafang Shao
2023-12-01 9:46 ` [PATCH v3 2/7] mm: mempolicy: Revise comment regarding mempolicy mode flags Yafang Shao
2023-12-01 9:46 ` [PATCH v3 3/7] mm, security: Fix missed security_task_movememory() Yafang Shao
2023-12-01 20:50 ` Serge E. Hallyn
2023-12-03 2:57 ` Yafang Shao
2023-12-01 9:46 ` [PATCH v3 4/7] mm, security: Add lsm hook for memory policy adjustment Yafang Shao
2023-12-01 9:46 ` [PATCH v3 5/7] security: selinux: Implement set_mempolicy hook Yafang Shao
2023-12-01 9:46 ` [PATCH v3 6/7] selftests/bpf: Add selftests for set_mempolicy with a lsm prog Yafang Shao
2023-12-01 9:46 ` Yafang Shao [this message]
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=20231201094636.19770-8-laoar.shao@gmail.com \
--to=laoar.shao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alx.manpages@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=jmorris@namei.org \
--cc=ligang.bdlg@bytedance.com \
--cc=linux-mm@kvack.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=mtk.manpages@gmail.com \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.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