From: "Michal Koutný" <mkoutny@suse.com>
To: Chen Ridong <chenridong@huaweicloud.com>
Cc: Waiman Long <llong@redhat.com>,
tj@kernel.org, hannes@cmpxchg.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org, lujialin4@huawei.com,
chenridong@huawei.com
Subject: Re: [PATCH -next v5 3/3] cpuset: add helpers for cpus read and cpuset_mutex locks
Date: Wed, 27 Aug 2025 10:46:43 +0200 [thread overview]
Message-ID: <vel3zxgvbrqfvw6drqrtbski7xwe2thn3bfeo6ahifuncvjxvu@kegptpfird5l> (raw)
In-Reply-To: <2b574bb7-0192-4a91-8925-bd4c6cc8a407@huaweicloud.com>
[-- Attachment #1: Type: text/plain, Size: 364 bytes --]
On Wed, Aug 27, 2025 at 02:23:17PM +0800, Chen Ridong <chenridong@huaweicloud.com> wrote:
> It was suggested to use a do-while construct for proper scoping. but it could not work if we define as:
Perhaps like this:
DEFINE_LOCK_GUARD_0(cpuset_full, cpuset_full_lock(), cpuset_full_unlock())
> So I sent this patch version.
No probs, it's a minor issue.
Michal
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 265 bytes --]
next prev parent reply other threads:[~2025-08-27 8:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 3:23 [PATCH -next v5 0/3] some optimization for cpuset Chen Ridong
2025-08-25 3:23 ` [PATCH -next v5 1/3] cpuset: decouple tmpmasks and cpumasks freeing in cgroup Chen Ridong
2025-08-25 3:23 ` [PATCH -next v5 2/3] cpuset: separate tmpmasks and cpuset allocation logic Chen Ridong
2025-08-25 17:37 ` Waiman Long
2025-08-25 3:23 ` [PATCH -next v5 3/3] cpuset: add helpers for cpus read and cpuset_mutex locks Chen Ridong
2025-08-26 14:23 ` Michal Koutný
2025-08-26 14:43 ` Waiman Long
2025-08-27 6:23 ` Chen Ridong
2025-08-27 8:46 ` Michal Koutný [this message]
2025-08-25 18:20 ` [PATCH -next v5 0/3] some optimization for cpuset Tejun Heo
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=vel3zxgvbrqfvw6drqrtbski7xwe2thn3bfeo6ahifuncvjxvu@kegptpfird5l \
--to=mkoutny@suse.com \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@huawei.com \
--cc=chenridong@huaweicloud.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llong@redhat.com \
--cc=lujialin4@huawei.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).