mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Lai Jiangshan <jiangshanlai@gmail.com>
Subject: [GIT PULL] workqueue fixes for v6.5-rc5
Date: Mon, 7 Aug 2023 09:57:26 -1000	[thread overview]
Message-ID: <ZNFMpjyxtKhnLrdK@slm.duckdns.org> (raw)

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(-)

             reply	other threads:[~2023-08-07 19:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07 19:57 Tejun Heo [this message]
2023-08-07 20:10 ` pr-tracker-bot

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=ZNFMpjyxtKhnLrdK@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=jiangshanlai@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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

all inboxes | Powered by JetHome®