From: Tejun Heo <tj@kernel.org>
To: Sven Schnelle <svens@linux.ibm.com>
Cc: Lai Jiangshan <jiangshanlai@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] workqueue: fix selection of wake_cpu in kick_pool()
Date: Tue, 16 Apr 2024 13:06:39 -1000 [thread overview]
Message-ID: <Zh8EfxdVdiIj_27H@slm.duckdns.org> (raw)
In-Reply-To: <20240415053550.538722-1-svens@linux.ibm.com>
Hello,
On Mon, Apr 15, 2024 at 07:35:49AM +0200, Sven Schnelle wrote:
> @@ -1277,7 +1277,8 @@ static bool kick_pool(struct worker_pool *pool)
> !cpumask_test_cpu(p->wake_cpu, pool->attrs->__pod_cpumask)) {
> struct work_struct *work = list_first_entry(&pool->worklist,
> struct work_struct, entry);
> - p->wake_cpu = cpumask_any_distribute(pool->attrs->__pod_cpumask);
> + p->wake_cpu = cpumask_any_and_distribute(pool->attrs->__pod_cpumask,
> + cpu_online_mask);
I think this can still race with the last CPU in the pod going down and
return nr_cpu_ids. Maybe something like the following would be better?
int wake_cpu;
wake_cpu = cpumask_any_distribute_and(...);
if (wake_cpu < nr_cpus_ids) {
p->wake_cpu = wake_cpu;
// update stat;
}
This generally seems like a good idea but isn't this still racy? The CPU may
go down between setting p->wake_cpu and wake_up_process().
Thanks.
--
tejun
next prev parent reply other threads:[~2024-04-16 23:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 5:35 Sven Schnelle
2024-04-16 23:06 ` Tejun Heo [this message]
2024-04-17 15:36 ` Sven Schnelle
2024-04-18 1:55 ` Tejun Heo
2024-04-18 5:54 ` Sven Schnelle
2024-04-18 15:56 ` Tejun Heo
2024-04-19 8:27 ` Sven Schnelle
2024-04-19 15:40 ` Tejun Heo
2024-04-22 22:44 ` Tejun Heo
2024-04-23 6:20 ` Sven Schnelle
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=Zh8EfxdVdiIj_27H@slm.duckdns.org \
--to=tj@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=svens@linux.ibm.com \
/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®