From: Randy Dunlap <rdunlap@infradead.org>
To: Gregory Price <gourry.memverge@gmail.com>, linux-mm@kvack.org
Cc: linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
linux-arch@vger.kernel.org, akpm@linux-foundation.org,
arnd@arndb.de, tglx@linutronix.de, luto@kernel.org,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
hpa@zytor.com, mhocko@kernel.org, tj@kernel.org,
ying.huang@intel.com, gregory.price@memverge.com, corbet@lwn.net,
rakie.kim@sk.com, hyeongtak.ji@sk.com, honggyu.kim@sk.com,
vtavarespetr@micron.com, peterz@infradead.org,
jgroves@micron.com, ravis.opensrc@micron.com,
sthanneeru@micron.com, emirakhur@micron.com, Hasan.Maruf@amd.com,
seungjun.ha@samsung.com, Frank van der Linden <fvdl@google.com>
Subject: Re: [PATCH v6 08/12] mm/mempolicy: add userland mempolicy arg structure
Date: Wed, 3 Jan 2024 16:19:03 -0800 [thread overview]
Message-ID: <429dd825-204a-4b11-87fd-ce9d39040d4d@infradead.org> (raw)
In-Reply-To: <20240103224209.2541-9-gregory.price@memverge.com>
Hi,
On 1/3/24 14:42, Gregory Price wrote:
> This patch adds the new user-api argument structure intended for
> set_mempolicy2 and mbind2.
>
> struct mpol_param {
> __u16 mode;
> __u16 mode_flags;
> __s32 home_node; /* mbind2: policy home node */
> __u16 pol_maxnodes;
> __u8 resv[6];
> __aligned_u64 *pol_nodes;
> };
>
> This structure is intended to be extensible as new mempolicy extensions
> are added.
>
> For example, set_mempolicy_home_node was added to allow vma mempolicies
> to have a preferred/home node assigned. This structure allows the user
> to set the home node at the time mempolicy is created, rather than
> requiring an additional syscalls.
>
> Full breakdown of arguments as of this patch:
> mode: Mempolicy mode (MPOL_DEFAULT, MPOL_INTERLEAVE)
>
> mode_flags: Flags previously or'd into mode in set_mempolicy
> (e.g.: MPOL_F_STATIC_NODES, MPOL_F_RELATIVE_NODES)
>
> home_node: for mbind2. Allows the setting of a policy's home
> with the use of MPOL_MF_HOME_NODE
>
> pol_maxnodes: Max number of nodes in the policy nodemask
>
> pol_nodes: Policy nodemask
>
> The reserved field accounts explicitly for a potential memory hole
> in the structure.
>
> Suggested-by: Frank van der Linden <fvdl@google.com>
> Suggested-by: Vinicius Tavares Petrucci <vtavarespetr@micron.com>
> Suggested-by: Hasan Al Maruf <Hasan.Maruf@amd.com>
> Signed-off-by: Gregory Price <gregory.price@memverge.com>
> Co-developed-by: Vinicius Tavares Petrucci <vtavarespetr@micron.com>
> Signed-off-by: Vinicius Tavares Petrucci <vtavarespetr@micron.com>
> ---
> .../admin-guide/mm/numa_memory_policy.rst | 17 +++++++++++++++++
> include/linux/syscalls.h | 1 +
> include/uapi/linux/mempolicy.h | 9 +++++++++
> 3 files changed, 27 insertions(+)
>
> diff --git a/Documentation/admin-guide/mm/numa_memory_policy.rst b/Documentation/admin-guide/mm/numa_memory_policy.rst
> index a70f20ce1ffb..cbfc5f65ed77 100644
> --- a/Documentation/admin-guide/mm/numa_memory_policy.rst
> +++ b/Documentation/admin-guide/mm/numa_memory_policy.rst
> @@ -480,6 +480,23 @@ closest to which page allocation will come from. Specifying the home node overri
> the default allocation policy to allocate memory close to the local node for an
> executing CPU.
>
> +Extended Mempolicy Arguments::
> +
> + struct mpol_param {
> + __u16 mode;
> + __u16 mode_flags;
> + __s32 home_node; /* mbind2: set home node */
> + __u64 pol_maxnodes;
> + __aligned_u64 pol_nodes; /* nodemask pointer */
> + };
>
Can you make the above documentation struct agree with the
struct in the header below, please?
(just a difference in the size of pol_maxnodes and the
'resv' bytes)
> +The extended mempolicy argument structure is defined to allow the mempolicy
> +interfaces future extensibility without the need for additional system calls.
> +
> +The core arguments (mode, mode_flags, pol_nodes, and pol_maxnodes) apply to
> +all interfaces relative to their non-extended counterparts. Each additional
> +field may only apply to specific extended interfaces. See the respective
> +extended interface man page for more details.
>
> Memory Policy Command Line Interface
> ====================================
> diff --git a/include/uapi/linux/mempolicy.h b/include/uapi/linux/mempolicy.h
> index 1f9bb10d1a47..109788c8be92 100644
> --- a/include/uapi/linux/mempolicy.h
> +++ b/include/uapi/linux/mempolicy.h
> @@ -27,6 +27,15 @@ enum {
> MPOL_MAX, /* always last member of enum */
> };
>
> +struct mpol_param {
> + __u16 mode;
> + __u16 mode_flags;
> + __s32 home_node; /* mbind2: policy home node */
> + __u16 pol_maxnodes;
> + __u8 resv[6];
> + __aligned_u64 pol_nodes;
> +};
> +
> /* Flags for set_mempolicy */
> #define MPOL_F_STATIC_NODES (1 << 15)
> #define MPOL_F_RELATIVE_NODES (1 << 14)
--
#Randy
next prev parent reply other threads:[~2024-01-04 0:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 22:41 [PATCH v6 00/12] mempolicy2, mbind2, and weighted interleave Gregory Price
2024-01-03 22:41 ` [PATCH v6 01/12] mm/mempolicy: implement the sysfs-based weighted_interleave interface Gregory Price
2024-01-03 22:41 ` [PATCH v6 02/12] mm/mempolicy: refactor a read-once mechanism into a function for re-use Gregory Price
2024-01-03 22:42 ` [PATCH v6 06/12] mm/mempolicy: refactor kernel_get_mempolicy for code re-use Gregory Price
2024-01-03 22:42 ` [PATCH v6 08/12] mm/mempolicy: add userland mempolicy arg structure Gregory Price
2024-01-04 0:19 ` Randy Dunlap [this message]
2024-01-04 2:03 ` Gregory Price
2024-01-10 20:11 ` [PATCH v6 00/12] mempolicy2, mbind2, and weighted interleave Gregory Price
2024-01-03 22:42 ` [PATCH v6 10/12] mm/mempolicy: add get_mempolicy2 syscall Gregory Price
2024-01-03 22:42 ` [PATCH v6 11/12] mm/mempolicy: add the mbind2 syscall Gregory Price
2024-01-03 22:42 ` [PATCH v6 12/12] mm/mempolicy: extend mempolicy2 and mbind2 to support weighted interleave Gregory Price
2024-01-11 3:41 ` [PATCH v6 00/12] mempolicy2, mbind2, and " Andi Kleen
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=429dd825-204a-4b11-87fd-ce9d39040d4d@infradead.org \
--to=rdunlap@infradead.org \
--cc=Hasan.Maruf@amd.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=emirakhur@micron.com \
--cc=fvdl@google.com \
--cc=gourry.memverge@gmail.com \
--cc=gregory.price@memverge.com \
--cc=honggyu.kim@sk.com \
--cc=hpa@zytor.com \
--cc=hyeongtak.ji@sk.com \
--cc=jgroves@micron.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mhocko@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rakie.kim@sk.com \
--cc=ravis.opensrc@micron.com \
--cc=seungjun.ha@samsung.com \
--cc=sthanneeru@micron.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=vtavarespetr@micron.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