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,
wuyun.abel@bytedance.com
Subject: Re: [PATCH] cgroup/cpuset: Add a new isolated mems.policy type.
Date: Mon, 5 Sep 2022 08:45:25 +0200 [thread overview]
Message-ID: <YxWbBYZKDTrkmlOe@dhcp22.suse.cz> (raw)
In-Reply-To: <20220904040241.1708-1-hezhongkun.hzk@bytedance.com>
On Sun 04-09-22 12:02:41, hezhongkun wrote:
> From: Zhongkun He <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 cpuset, and we can control low-priority cgroups to
> allocate memory in specified nodes. So this patch want to
> adds the mempolicy interface in cpuset.
>
> The mempolicy priority of cpuset is lower than the task.
> The order of getting the policy is:
> 1) vma mempolicy
> 2) task->mempolicy
> 3) cpuset->mempolicy
> 4) default policy.
>
> cpuset's policy is owned by itself, but descendants will
> get the default mempolicy from parent.
What is the hierarchical behavior of the policy? Say parent has a
stronger requirement (say bind) than a child (prefer)?
> How to use the mempolicy interface:
> echo prefer:2 > /sys/fs/cgroup/zz/cpuset.mems.policy
> echo bind:1-3 > /sys/fs/cgroup/zz/cpuset.mems.policy
> echo interleave:0,1,2,3 >/sys/fs/cgroup/zz/cpuset.mems.policy
Am I just confused or did you really mean to combine all these
together?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2022-09-05 6:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-04 4:02 [PATCH] cgroup/cpuset: Add a new isolated mems.policy type hezhongkun
2022-09-04 6:04 ` kernel test robot
2022-09-04 6:20 ` kernel test robot
2022-09-04 6:41 ` kernel test robot
2022-09-04 23:08 ` kernel test robot
2022-09-05 6:45 ` Michal Hocko [this message]
2022-09-05 10:30 ` [External] " Zhongkun He
2022-09-05 10:50 ` Michal Hocko
2022-09-06 10:37 ` Zhongkun He
2022-09-06 12:33 ` Michal Hocko
2022-09-07 13:50 ` Zhongkun He
2022-09-08 7:19 ` Michal Hocko
2022-09-09 2:55 ` Zhongkun He
2022-09-14 15:10 ` Zhongkun He
2022-09-23 7:29 ` Michal Hocko
2022-09-23 15:26 ` Zhongkun He
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=YxWbBYZKDTrkmlOe@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 \
--cc=wuyun.abel@bytedance.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;
as well as URLs for NNTP newsgroup(s).