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: Re: [PATCH -next v3 0/3] some optimization for cpuset
Date: Mon, 18 Aug 2025 14:54:37 +0800 [thread overview]
Message-ID: <63846dd9-3b5d-4a27-be6e-754dadfa5444@huaweicloud.com> (raw)
In-Reply-To: <20250818034430.1304069-1-chenridong@huaweicloud.com>
On 2025/8/18 11:44, Chen Ridong wrote:
> 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.
>
> ---
> 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(-)
>
Sorry for forgetting to update the commit message for patch 3. Please ignore this series.
--
Best regards,
Ridong
prev parent reply other threads:[~2025-08-18 6:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 3:44 [PATCH -next v3 0/3] some optimization for cpuset Chen Ridong
2025-08-18 3:44 ` [PATCH -next v3 1/3] cpuset: decouple tmpmasks and cpumasks freeing in cgroup Chen Ridong
2025-08-18 3:44 ` [PATCH -next v3 2/3] cpuset: separate tmpmasks and cpuset allocation logic Chen Ridong
2025-08-18 3:44 ` [PATCH -next v3 3/3] cpuset: add helpers for cpus read and cpuset_mutex locks Chen Ridong
2025-08-18 6:54 ` Chen Ridong [this message]
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=63846dd9-3b5d-4a27-be6e-754dadfa5444@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).