From: Tejun Heo <tj@kernel.org>
To: Michal Blaszczyk <michalblk@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
David Vernet <void@manifault.com>,
Andrea Righi <arighi@nvidia.com>,
Changwoo Min <changwoo@igalia.com>,
Kuba Piecuch <jpiecuch@google.com>,
sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] sched: Lift cgroup update locking to core to prevent CFS/SCX divergence
Date: Fri, 21 Aug 2026 09:08:09 -1000 [thread overview]
Message-ID: <aoiiGQttAjhxe8HK@slm.duckdns.org> (raw)
In-Reply-To: <20260821140818.1559100-1-michalblk@google.com>
On Fri, Aug 21, 2026 at 02:08:18PM +0000, Michal Blaszczyk wrote:
> +DEFINE_MUTEX(shares_mutex);
Maybe cpu_weight_mutex?
> +static DEFINE_MUTEX(cfs_constraints_mutex);
and cpu_max_mutex?
Thanks.
--
tejun
prev parent reply other threads:[~2026-08-21 19:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 16:09 [PATCH] sched: Serialize cgroup updates to prevent CFS/SCX state divergence Michal Blaszczyk
2026-08-20 17:21 ` Tejun Heo
2026-08-21 7:26 ` Peter Zijlstra
2026-08-21 14:08 ` [PATCH v2] sched: Lift cgroup update locking to core to prevent CFS/SCX divergence Michal Blaszczyk
2026-08-21 19:08 ` Tejun Heo [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=aoiiGQttAjhxe8HK@slm.duckdns.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=jpiecuch@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michalblk@google.com \
--cc=peterz@infradead.org \
--cc=sched-ext@lists.linux.dev \
--cc=void@manifault.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
all inboxes | Powered by JetHome®