From: Michal Hocko <mhocko@suse.com>
To: 贺中坤 <hezhongkun.hzk@bytedance.com>
Cc: hannes@cmpxchg.org, roman.gushchin@linux.dev,
linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
linux-mm@kvack.org, lizefan.x@bytedance.com
Subject: Re: [External] Re: [PATCH] mm: memcontrol: add the mempolicy interface for cgroup v2.
Date: Tue, 24 May 2022 14:04:33 +0200 [thread overview]
Message-ID: <YozJ0SNOjO3m4ehp@dhcp22.suse.cz> (raw)
In-Reply-To: <CACSyD1N4VeWBOzZwBogDW-wBbLvF54VrZ1Z+p9NFiXY+etuDJA@mail.gmail.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Michal Hocko <mhocko-IBi9RG/b67k@public.gmane.org>
To: 贺中坤 <hezhongkun.hzk-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org>
Cc: hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org,
roman.gushchin-fxUVXftIFDnyG1zEObXtfA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
lizefan.x-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org
Subject: Re: [External] Re: [PATCH] mm: memcontrol: add the mempolicy interface for cgroup v2.
Date: Tue, 24 May 2022 14:04:33 +0200 [thread overview]
Message-ID: <YozJ0SNOjO3m4ehp@dhcp22.suse.cz> (raw)
In-Reply-To: <CACSyD1N4VeWBOzZwBogDW-wBbLvF54VrZ1Z+p9NFiXY+etuDJA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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
next prev parent reply other threads:[~2022-05-24 12:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 10:36 [PATCH] mm: memcontrol: add the mempolicy interface for cgroup v2 hezhongkun
2022-05-24 10:36 ` hezhongkun
2022-05-24 10:47 ` Michal Hocko
2022-05-24 10:47 ` Michal Hocko
2022-05-24 11:46 ` [External] " 贺中坤
2022-05-24 12:04 ` Michal Hocko [this message]
2022-05-24 12:04 ` Michal Hocko
2022-05-24 13:10 ` kernel test robot
2022-05-24 13:10 ` kernel test robot
2022-05-24 15:02 ` kernel test robot
2022-05-24 15:02 ` kernel test robot
2022-05-24 15:12 ` kernel test robot
2022-05-24 15:12 ` kernel test robot
2022-05-25 7:56 ` [mm] 6adb0a02c2: WARNING:suspicious_RCU_usage kernel test robot
2022-05-25 7:56 ` kernel test robot
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=YozJ0SNOjO3m4ehp@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=hezhongkun.hzk@bytedance.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan.x@bytedance.com \
--cc=roman.gushchin@linux.dev \
/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.