From: Mathias Koehrer <mathias.koehrer@etas.com>
To: Josh Cartwright <joshc@ni.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: Kernel thread's CPU affinity with isolcpus kernel boot argument
Date: Fri, 26 Feb 2016 11:53:53 +0100 [thread overview]
Message-ID: <56D02EC1.6000403@etas.com> (raw)
In-Reply-To: <20160225144308.GG9598@jcartwri.amer.corp.natinst.com>
Am 25.02.2016 um 15:43 schrieb Josh Cartwright:
> On Thu, Feb 25, 2016 at 03:18:06PM +0100, Sebastian Andrzej Siewior wrote:
>> * Mathias Koehrer | 2016-01-15 12:15:28 [+0100]:
>>
>>> However, I noticed that most kernel threads use the affinity mask 0xff.
>>> I can change this by using ???taskset???. However, I am wondering if
>>> there is mechanism that forces the kernel to consider the value of
>>> ???isolcpus??? also for kernel threads.
>>
>> not that I am aware of. There are a few per-CPU threads which have to
>> stay the way they are. I would have expected that others like kworker/u*
>> respect the isol CPUs and stay away.
>
> I suppose the higher level question to Mathias is: are you seeing these
> threads perturb your application? Or, are you just observing they are
> affinitized to isolcpus?
We use isolcpus=1-31 to reserve all cores but core 0 for real time stuff.
I just noticed, that some kernel threads have an affinity to cores > 0.
So far I did not observe any disturbance from these threads.
Thanks
Mathias
next prev parent reply other threads:[~2016-02-26 10:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 11:15 Kernel thread's CPU affinity with isolcpus kernel boot argument Mathias Koehrer
2016-02-25 14:18 ` Sebastian Andrzej Siewior
2016-02-25 14:43 ` Josh Cartwright
2016-02-26 10:53 ` Mathias Koehrer [this message]
2016-02-25 15:13 ` Daniel Bristot de Oliveira
2016-02-25 16:35 ` Sebastian Andrzej Siewior
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=56D02EC1.6000403@etas.com \
--to=mathias.koehrer@etas.com \
--cc=bigeasy@linutronix.de \
--cc=joshc@ni.com \
--cc=linux-rt-users@vger.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;
as well as URLs for NNTP newsgroup(s).