From: Tejun Heo <tj@kernel.org>
To: Tal Shorer <tal.shorer@gmail.com>
Cc: jiangshanlai@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] workqueue: respect isolated cpus when queueing an unbound work
Date: Sat, 21 Oct 2017 08:49:46 -0700 [thread overview]
Message-ID: <20171021154946.GL1302522@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <1508449446-23693-1-git-send-email-tal.shorer@gmail.com>
On Fri, Oct 20, 2017 at 12:44:06AM +0300, Tal Shorer wrote:
> Initialize wq_unbound_cpumask to exclude cpus that were isolated by
> the cmdline's isolcpus parameter.
>
> Signed-off-by: Tal Shorer <tal.shorer@gmail.com>
> ---
> kernel/workqueue.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/workqueue.c b/kernel/workqueue.c
> index ca937b0..25b351d 100644
> --- a/kernel/workqueue.c
> +++ b/kernel/workqueue.c
> @@ -5546,7 +5546,7 @@ int __init workqueue_init_early(void)
> WARN_ON(__alignof__(struct pool_workqueue) < __alignof__(long long));
>
> BUG_ON(!alloc_cpumask_var(&wq_unbound_cpumask, GFP_KERNEL));
> - cpumask_copy(wq_unbound_cpumask, cpu_possible_mask);
> + cpumask_andnot(wq_unbound_cpumask, cpu_possible_mask, cpu_isolated_map);
Don't we also wanna apply the same masking when wq_unbound_cpumask is
being updated after boot?
Thanks.
--
tejun
next prev parent reply other threads:[~2017-10-21 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 21:44 [PATCH] workqueue: respect isolated cpus when queueing an unbound work Tal Shorer
2017-10-21 15:49 ` Tejun Heo [this message]
[not found] ` <CAFDyS3Mgt=Vt-sJXVL_pY_DwrC2dDTDQ0jMNyAbCwvLptu88Sw@mail.gmail.com>
[not found] ` <20171021160446.GO1302522@devbig577.frc2.facebook.com>
2017-10-21 16:13 ` Tal Shorer
2017-10-21 16:15 ` Tejun Heo
2017-10-21 16:29 ` [PATCH v2] " Tal Shorer
2017-10-21 16:33 ` Tejun Heo
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=20171021154946.GL1302522@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tal.shorer@gmail.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