Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: Sasha Levin <sashal@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH AUTOSEL 4.19 12/14] workqueue: Call wq_update_unbound_numa() on all CPUs in NUMA node on CPU hotplug
Date: Mon, 11 Sep 2023 11:57:47 +0200	[thread overview]
Message-ID: <ZP7kmzEAizx8MU/Z@duo.ucw.cz> (raw)
In-Reply-To: <20230909004045.3581014-12-sashal@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 785 bytes --]

Hi!

> When a CPU went online or offline, wq_update_unbound_numa() was called only
> on the CPU which was going up or down. This works fine because all CPUs on
> the same NUMA node share the same pool_workqueue slot - one CPU updating it
> updates it for everyone in the node.
> 
> However, future changes will make each CPU use a separate pool_workqueue
> even when they're sharing the same worker_pool, which requires updating
> pool_workqueue's for all CPUs which may be sharing the same pool_workqueue
> on hotplug.

Yes, but we are not porting those future changes to stable, right?
Please drop.

BR,
									Pavel
-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2023-09-11 22:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-09  0:40 [PATCH AUTOSEL 4.19 01/14] media: dvb-usb-v2: af9035: Fix null-ptr-deref in af9035_i2c_master_xfer Sasha Levin
2023-09-09  0:40 ` [PATCH AUTOSEL 4.19 02/14] media: dw2102: Fix null-ptr-deref in dw2102_i2c_transfer() Sasha Levin
2023-09-09  0:40 ` [PATCH AUTOSEL 4.19 03/14] media: af9005: Fix null-ptr-deref in af9005_i2c_xfer Sasha Levin
2023-09-09  0:40 ` [PATCH AUTOSEL 4.19 04/14] media: anysee: fix null-ptr-deref in anysee_master_xfer Sasha Levin
2023-09-09  0:40 ` [PATCH AUTOSEL 4.19 05/14] media: az6007: Fix null-ptr-deref in az6007_i2c_xfer() Sasha Levin
2023-09-09  0:40 ` [PATCH AUTOSEL 4.19 06/14] iio: core: Use min() instead of min_t() to make code more robust Sasha Levin
2023-09-09  0:40 ` [PATCH AUTOSEL 4.19 07/14] media: tuners: qt1010: replace BUG_ON with a regular error Sasha Levin
2023-09-09  0:40 ` [PATCH AUTOSEL 4.19 08/14] media: pci: cx23885: replace BUG with error return Sasha Levin
2023-09-09  0:40 ` [PATCH AUTOSEL 4.19 09/14] usb: gadget: fsl_qe_udc: validate endpoint index for ch9 udc Sasha Levin
2023-09-09  0:40 ` [PATCH AUTOSEL 4.19 10/14] scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show() Sasha Levin
2023-09-09  0:40 ` [PATCH AUTOSEL 4.19 11/14] serial: cpm_uart: Avoid suspicious locking Sasha Levin
2023-09-09  0:40 ` [PATCH AUTOSEL 4.19 12/14] workqueue: Call wq_update_unbound_numa() on all CPUs in NUMA node on CPU hotplug Sasha Levin
2023-09-11  9:57   ` Pavel Machek [this message]
2023-09-09  0:40 ` [PATCH AUTOSEL 4.19 13/14] media: pci: ipu3-cio2: Initialise timing struct to avoid a compiler warning Sasha Levin
2023-09-09  0:40 ` [PATCH AUTOSEL 4.19 14/14] kobject: Add sanity check for kset->kobj.ktype in kset_register() Sasha Levin

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=ZP7kmzEAizx8MU/Z@duo.ucw.cz \
    --to=pavel@denx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tj@kernel.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