From: Tejun Heo <tj@kernel.org>
To: Tal Shorer <tal.shorer@gmail.com>
Cc: jiangshanlai@gmail.com,
"<linux-kernel@vger.kernel.org>" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] workqueue: respect isolated cpus when queueing an unbound work
Date: Sat, 21 Oct 2017 09:15:33 -0700 [thread overview]
Message-ID: <20171021161533.GQ1302522@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <CAFDyS3MsrhZu71L2c=Q0fps-x_WRtB=ocx+4N1G+3ne3Yr8Ehg@mail.gmail.com>
Hello,
On Sat, Oct 21, 2017 at 07:13:33PM +0300, Tal Shorer wrote:
> > Do we have a consistent behavior around this? Are there different
> > examples where isolcpus interact with other dynamically configurable
> > parameters?
> >
> sched_setaffinity comes to mind, which obviously bypasses isolcpus.
> Running git grep, other uses of cpu_isolated_map are just its
> initialization and its use and the initialization of
> non_isolated_cpus.
Can you add a comment explaining that it's intentional that we only
follow isolcpus during boot and allow later overrides?
Thanks.
--
tejun
next prev parent reply other threads:[~2017-10-21 16:15 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
[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 [this message]
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=20171021161533.GQ1302522@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