From: Abel Wu <wuyun.abel@bytedance.com>
To: akpm@linux-foundation.org, lizefan.x@bytedance.com,
tj@kernel.org, hannes@cmpxchg.org, corbet@lwn.net
Cc: cgroups@vger.kernel.org, linux-mm@kvack.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Abel Wu <wuyun.abel@bytedance.com>
Subject: [PATCH 0/3] cgroup2: introduce cpuset.mems.migration
Date: Mon, 26 Apr 2021 14:59:43 +0800 [thread overview]
Message-ID: <20210426065946.40491-1-wuyun.abel@bytedance.com> (raw)
Some of our services are quite performance sensitive and
actually NUMA-aware designed, aka numa-service. The SLOs
can be easily violated when co-locate numa-services with
other workloads. Thus they are granted to occupy the whole
NUMA node and when such assignment applies, the workload
on that node needs to be moved away fast and complete.
This new cgroup v2 interface is an enhancement of cgroup
v1 interface cpuset.memory_migrate by adding a new mode
called "lazy". With the help of the "lazy" mode migration
we solved the aforementioned problem on fast eviction.
Patch 1 applies cpusets limits to tasks that using default
memory policies, which makes pages inside mems_allowed are
preferred when autoNUMA is enabled. This is also necessary
for the "lazy" mode of cpuset.mems.migration.
Patch 2&3 introduce cpuset.mems.migration, see the patches
for detailed information please.
Abel Wu (3):
mm/mempolicy: apply cpuset limits to tasks using default policy
cgroup/cpuset: introduce cpuset.mems.migration
docs/admin-guide/cgroup-v2: add cpuset.mems.migration
Documentation/admin-guide/cgroup-v2.rst | 36 ++++++++
kernel/cgroup/cpuset.c | 104 +++++++++++++++++++-----
mm/mempolicy.c | 7 +-
3 files changed, 124 insertions(+), 23 deletions(-)
--
2.31.1
next reply other threads:[~2021-04-26 7:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 6:59 Abel Wu [this message]
2021-04-26 6:59 ` [PATCH 1/3] mm/mempolicy: apply cpuset limits to tasks using default policy Abel Wu
2021-04-26 6:59 ` [PATCH 2/3] cgroup/cpuset: introduce cpuset.mems.migration Abel Wu
2021-04-27 14:43 ` Tejun Heo
2021-04-28 7:24 ` Abel Wu
2021-05-05 5:06 ` [Phishing Risk] [External] " Abel Wu
2021-05-05 22:30 ` Johannes Weiner
2021-04-26 6:59 ` [PATCH 3/3] docs/admin-guide/cgroup-v2: add cpuset.mems.migration Abel Wu
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=20210426065946.40491-1-wuyun.abel@bytedance.com \
--to=wuyun.abel@bytedance.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=hannes@cmpxchg.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan.x@bytedance.com \
--cc=tj@kernel.org \
/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).