[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1cacc295-ccea-4725-913c-7c95efeec776@huaweicloud.com>
Date: Tue, 19 Aug 2025 09:56:55 +0800
From: Chen Ridong <chenridong@...weicloud.com>
To: Tejun Heo <tj@...nel.org>
Cc: hannes@...xchg.org, mkoutny@...e.com, lizefan@...wei.com,
cgroups@...r.kernel.org, linux-kernel@...r.kernel.org, lujialin4@...wei.com,
chenridong@...wei.com, hdanton@...a.com, gaoyingjie@...ontech.com
Subject: Re: [PATCH v5] cgroup: split cgroup_destroy_wq into 3 workqueues
On 2025/8/19 1:08, Tejun Heo wrote:
> Hello,
>
> On Mon, Aug 18, 2025 at 06:14:35AM +0000, Chen Ridong wrote:
> ...
>> + * Rationale for using separate workqueues:
>> + * The cgroup root free work may depend on completion of other css offline
>> + * operations. If all tasks were enqueued to a single workqueue, this could
>> + * create a deadlock scenario where:
>> + * - Free work waits for other css offline work to complete.
>> + * - But other css offline work is queued after free work in the same queue.
>
> Can you please refer to the concrete example too?
>
> Thanks.
>
Sure, the comment has been updated in v6. Please let me know if you have any feedback.
--
Best regards,
Ridong
Powered by blists - more mailing lists