From: Chen Ridong <chenridong@huaweicloud.com>
To: longman@redhat.com, tj@kernel.org, hannes@cmpxchg.org, mkoutny@suse.com
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
lujialin4@huawei.com, chenridong@huawei.com
Subject: [PATCH -next v4 0/3] some optimization for cpuset
Date: Mon, 18 Aug 2025 06:41:38 +0000 [thread overview]
Message-ID: <20250818064141.1334859-1-chenridong@huaweicloud.com> (raw)
From: Chen Ridong <chenridong@huawei.com>
This patch series contains several cpuset improvements:
1. Decouple cpuset and tmpmasks allocation/freeing.
2. Add cpuset_full_[un]lock helpers.
---
v4:
- update the commit message for patch 3.
v3:
- fix typos and comment errors.
- rename cpus_read_cpuset_[un]lock to cpuset_full_[un]lock
v2:
- dropped guard helper approach, nusing new helper instead.
- added patches for decoupling cpuset/tmpmasks allocation
Chen Ridong (3):
cpuset: decouple tmpmasks and cpumasks freeing in cgroup
cpuset: separate tmpmasks and cpuset allocation logic
cpuset: add helpers for cpus read and cpuset_mutex locks
kernel/cgroup/cpuset-internal.h | 2 +
kernel/cgroup/cpuset-v1.c | 12 +-
kernel/cgroup/cpuset.c | 220 +++++++++++++++++---------------
3 files changed, 122 insertions(+), 112 deletions(-)
--
2.34.1
next reply other threads:[~2025-08-18 6:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 6:41 Chen Ridong [this message]
2025-08-18 6:41 ` [PATCH -next v4 1/3] cpuset: decouple tmpmasks and cpumasks freeing in cgroup Chen Ridong
2025-08-24 17:07 ` Waiman Long
2025-08-18 6:41 ` [PATCH -next v4 2/3] cpuset: separate tmpmasks and cpuset allocation logic Chen Ridong
2025-08-24 17:05 ` Waiman Long
2025-08-25 0:52 ` Chen Ridong
2025-08-18 6:41 ` [PATCH -next v4 3/3] cpuset: add helpers for cpus read and cpuset_mutex locks Chen Ridong
2025-08-24 17:07 ` Waiman Long
2025-08-23 2:08 ` [PATCH -next v4 0/3] some optimization for cpuset Chen Ridong
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=20250818064141.1334859-1-chenridong@huaweicloud.com \
--to=chenridong@huaweicloud.com \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@huawei.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=lujialin4@huawei.com \
--cc=mkoutny@suse.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).