[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1b70929f-1f73-c549-64c1-94cea2c1a36c@acm.org>
Date: Tue, 15 Feb 2022 09:05:38 -0800
From: Bart Van Assche <bvanassche@....org>
To: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>,
Haakon Bugge <haakon.bugge@...cle.com>
Cc: Tejun Heo <tj@...nel.org>,
syzbot <syzbot+831661966588c802aae9@...kaller.appspotmail.com>,
Jason Gunthorpe <jgg@...pe.ca>,
LKML <linux-kernel@...r.kernel.org>,
OFED mailing list <linux-rdma@...r.kernel.org>,
"syzkaller-bugs@...glegroups.com" <syzkaller-bugs@...glegroups.com>,
Lai Jiangshan <jiangshanlai@...il.com>
Subject: Re: [syzbot] possible deadlock in worker_thread
On 2/15/22 04:48, Tetsuo Handa wrote:
> I do not want to do like
>
> - system_wq = alloc_workqueue("events", 0, 0);
> + system_wq = alloc_workqueue("events", __WQ_SYSTEM_WIDE, 0);
>
> because the intent of this change is to ask developers to create their own WQs.
I want more developers to use the system-wide workqueues since that
reduces memory usage. That matters for embedded devices running Linux.
Thanks,
Bart.
Powered by blists - more mailing lists