Re: Performance drop due to alloc_workqueue() misuse and recent change
From: Tejun Heo <tj@kernel.org>
Date: 2023-12-20 07:15:02
Also in:
ceph-devel, cgroups, dm-devel, dri-devel, gfs2, intel-gfx, linux-arm-kernel, linux-bcachefs, linux-block, linux-btrfs, linux-cifs, linux-crypto, linux-f2fs-devel, linux-fscrypt, linux-iommu, linux-media, linux-mediatek, linux-mm, linux-mmc, linux-nfs, linux-nvme, linux-rdma, linux-remoteproc, linux-scsi, linux-trace-kernel, linux-usb, linux-wireless, linux-xfs, lkml, netdev, platform-driver-x86, target-devel, virtualization
Hello, again. On Mon, Dec 04, 2023 at 04:03:47PM +0000, Naohiro Aota wrote: ...
In summary, we misuse max_active, considering it is a global limit. And, the recent commit introduced a huge performance drop in some cases. We need to review alloc_workqueue() usage to check if its max_active setting is proper or not.
Can you please test the following branch? https://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git unbound-system-wide-max_active Thanks. -- tejun