From: Michal Hocko <mhocko@suse.com>
To: hezhongkun <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: [PATCH] mm: memcontrol: add the mempolicy interface for cgroup v2.
Date: Tue, 24 May 2022 12:47:28 +0200 [thread overview]
Message-ID: <Yoy3wDh0cvziWGHJ@dhcp22.suse.cz> (raw)
In-Reply-To: <20220524103638.473-1-hezhongkun.hzk@bytedance.com>
On Tue 24-05-22 18:36:38, hezhongkun wrote:
> From: Hezhongkun <hezhongkun.hzk@bytedance.com>
>
> Mempolicy is difficult to use because it is set in-process
> via a system call. We want to make it easier to use mempolicy
> in cgroups, so that we can control low-priority cgroups to
> allocate memory in specified nodes. So this patch want to
> adds the mempolicy interface.
>
> the mempolicy priority of memcgroup is higher than the priority
> of task. The order of getting the policy is,
> memcgroup->policy,task->policy or vma policy, default policy.
> memcgroup's policy is owned by itself, so descendants will
> not inherit it.
Why cannot you use cpuset cgroup?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2022-05-24 10:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 10:36 hezhongkun
2022-05-24 10:47 ` Michal Hocko [this message]
2022-05-24 11:46 ` [External] " 贺中坤
2022-05-24 12:04 ` Michal Hocko
2022-05-24 13:10 ` kernel test robot
2022-05-24 15:02 ` 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
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=Yoy3wDh0cvziWGHJ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox