[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZNFMpjyxtKhnLrdK@slm.duckdns.org>
Date: Mon, 7 Aug 2023 09:57:26 -1000
From: Tejun Heo <tj@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org,
Lai Jiangshan <jiangshanlai@...il.com>
Subject: [GIT PULL] workqueue fixes for v6.5-rc5
The following changes since commit 3f01e9fed8454dcd89727016c3e5b2fbb8f8e50c:
Merge tag 'linux-watchdog-6.5-rc2' of git://www.linux-watchdog.org/linux-watchdog (2023-07-10 10:04:26 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git/ tags/wq-for-6.5-rc5-fixes
for you to fetch changes up to aa6fde93f3a49e42c0fe0490d7f3711bac0d162e:
workqueue: Scale up wq_cpu_intensive_thresh_us if BogoMIPS is below 4000 (2023-07-25 11:49:57 -1000)
----------------------------------------------------------------
workqueue: Fixes for v6.5-rc5
Two commits:
* The recently added cpu_intensive auto detection and warning mechanism was
spuriously triggered on slow CPUs. While not causing serious issues, it's
still a nuisance and can cause unintended concurrency management
behaviors. Relax the threshold on machines with lower BogoMIPS. While
BogoMIPS is not an accurate measure of performance by most measures, we
don't have to be accurate and it has rough but strong enough correlation.
* A correction in Kconfig help text.
----------------------------------------------------------------
Geert Uytterhoeven (1):
workqueue: Fix cpu_intensive_thresh_us name in help text
Tejun Heo (1):
workqueue: Scale up wq_cpu_intensive_thresh_us if BogoMIPS is below 4000
kernel/workqueue.c | 43 ++++++++++++++++++++++++++++++++++++++++++-
lib/Kconfig.debug | 2 +-
2 files changed, 43 insertions(+), 2 deletions(-)
Powered by blists - more mailing lists