All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Yafang Shao <laoar.shao@gmail.com>
Cc: linux-mm@kvack.org, "Huang, Ying" <ying.huang@intel.com>
Subject: Re: [PATCH] mbind.2: Add mode flag MPOL_F_NUMA_BALANCING
Date: Sat, 9 Dec 2023 12:35:46 +0100	[thread overview]
Message-ID: <ZXRREoA7OCfLYOLu@debian> (raw)
In-Reply-To: <20231208090553.4285-1-laoar.shao@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1859 bytes --]

Hello Yafang,

On Fri, Dec 08, 2023 at 09:05:53AM +0000, Yafang Shao wrote:
> 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
> 
> Suggested-by: "Huang, Ying" <ying.huang@intel.com>
> 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>
> ---

Patch applied.

Thanks,
Alex

>  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.30.1 (Apple Git-130)
> 

-- 
<https://www.alejandro-colomar.es/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

           reply	other threads:[~2023-12-09 11:35 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20231208090553.4285-1-laoar.shao@gmail.com>]

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=ZXRREoA7OCfLYOLu@debian \
    --to=alx@kernel.org \
    --cc=laoar.shao@gmail.com \
    --cc=linux-mm@kvack.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.