mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Waiman Long <llong@redhat.com>
Cc: Chen Ridong <chenridong@huaweicloud.com>,
	hannes@cmpxchg.org, mkoutny@suse.com, cgroups@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] cgroup/cpuset: remove kernfs active break
Date: Wed, 8 Jan 2025 09:35:36 -1000	[thread overview]
Message-ID: <Z37TiId4rFkwc0Mc@slm.duckdns.org> (raw)
In-Reply-To: <c40d5b49-1955-42ee-b95c-37ed580e9933@redhat.com>

Hello,

On Wed, Jan 08, 2025 at 02:27:07PM -0500, Waiman Long wrote:
> On 1/8/25 11:53 AM, Tejun Heo wrote:
> This patch looks good me. However, this does raise a question that I
> overlook when I made hotplug operation synchronous while task transfer, if
> needed, remained asynchronous. There is a very slight chance where we keep
> removing tasks added after execution capability is restored. As cgroup v1 is
> in the process of being deprecated, do you think we still need to do
> something to address this issue?

I *think* that should be fine. In cgroup1, the kernel is making irreversible
system config changes when a cgroup loses all its CPUs. I have a hard time
imagining use cases that would depend on the the exact ordering of
operations at that point. The auto transfer-out was always the last ditch
measure to not leave the system in a broken state after all. If someone's
depending on the transfer out being strictly ordered w.r.t. the cgroup
losing all CPUs and then gaining some, let's hear why the hell that ordering
matters first.

Thanks.

-- 
tejun

  reply	other threads:[~2025-01-08 19:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-06  8:19 Chen Ridong
2025-01-08 16:53 ` Tejun Heo
2025-01-08 19:27   ` Waiman Long
2025-01-08 19:35     ` Tejun Heo [this message]
2025-01-08 19:50       ` Waiman Long
2025-01-08 20:00         ` Tejun Heo
2025-01-08 20:04           ` Waiman Long
2025-01-08 19:20 ` Waiman Long
2025-01-08 19:23 ` Tejun Heo
2025-01-09  1:29   ` Chen Ridong
2025-01-09  1:55     ` Tejun Heo
2025-01-09  2:07       ` 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=Z37TiId4rFkwc0Mc@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=chenridong@huaweicloud.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llong@redhat.com \
    --cc=mkoutny@suse.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®