From: Tejun Heo <tj@kernel.org>
To: Chen Ridong <chenridong@huaweicloud.com>
Cc: "Roman Gushchin" <roman.gushchin@linux.dev>,
"Michal Koutný" <mkoutny@suse.com>,
"Chen Ridong" <chenridong@huawei.com>,
martin.lau@linux.dev, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@google.com, haoluo@google.com,
jolsa@kernel.org, lizefan.x@bytedance.com, hannes@cmpxchg.org,
bpf@vger.kernel.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/1] cgroup: fix deadlock caused by cgroup_mutex and cpu_hotplug_lock
Date: Wed, 11 Sep 2024 19:59:48 -1000 [thread overview]
Message-ID: <ZuKDVMTvy5Q8evSx@slm.duckdns.org> (raw)
In-Reply-To: <83cea8c6-d2f8-42f2-990e-80412ebf296e@huaweicloud.com>
On Thu, Sep 12, 2024 at 09:33:23AM +0800, Chen Ridong wrote:
> I will add a patch do document that.
> Should we modify WQ_DFL_ACTIVE(256 now)? Maybe 1024 is acceptable?
Yeah, let's bump it.
Thanks.
--
tejun
next prev parent reply other threads:[~2024-09-12 5:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-17 9:33 [PATCH v3 0/1] Fix deadlock caused by cgroup_mutex and cpu_hotplug_lock Chen Ridong
2024-08-17 9:33 ` [PATCH v3 1/1] cgroup: fix " Chen Ridong
2024-08-22 0:57 ` Chen Ridong
2024-08-30 2:08 ` Chen Ridong
2024-09-09 14:19 ` Michal Koutný
2024-09-10 1:31 ` Chen Ridong
2024-09-10 21:02 ` Roman Gushchin
2024-09-10 21:17 ` Tejun Heo
2024-09-12 1:33 ` Chen Ridong
2024-09-12 5:59 ` Tejun Heo [this message]
2024-09-11 11:15 ` Hillf Danton
2024-09-26 12:53 ` Michal Koutný
2024-09-27 11:25 ` Hillf Danton
2024-09-27 14:03 ` Michal Koutný
2024-09-28 8:11 ` Tetsuo Handa
2024-09-29 1:30 ` 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=ZuKDVMTvy5Q8evSx@slm.duckdns.org \
--to=tj@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@huawei.com \
--cc=chenridong@huaweicloud.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=martin.lau@linux.dev \
--cc=mkoutny@suse.com \
--cc=roman.gushchin@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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