linux-kernel - Re: [External] Re: [PATCH] mm: memcontrol: add the mempolicy interface for cgroup v2.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <YozJ0SNOjO3m4ehp@dhcp22.suse.cz>
Date:   Tue, 24 May 2022 14:04:33 +0200
From:   Michal Hocko <mhocko@...e.com>
To:     贺中坤 <hezhongkun.hzk@...edance.com>
Cc:     hannes@...xchg.org, roman.gushchin@...ux.dev,
        linux-kernel@...r.kernel.org, cgroups@...r.kernel.org,
        linux-mm@...ck.org, lizefan.x@...edance.com
Subject: Re: [External] Re: [PATCH] mm: memcontrol: add the mempolicy
 interface for cgroup v2.

On Tue 24-05-22 19:46:38, 贺中坤 wrote:
> Hi Michal, thanks for your reply.
> mempolicy has two functions, which nodes to choose and how to use these
> nodes. cpuset can only decide the first one，it equal to 'bind' mempolicy.
> If cgroups support mempolicy, we can continue to develop more policy
> types. For example, allocate memory according to node weight, etc.
> We would like to have more precise control over memory allocation in NUMA
> server.

Why cputset controller cannot be extended instead?

-- 
Michal Hocko
SUSE Labs