From: Josh Cartwright <joshc@ni.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Mathias Koehrer <mathias.koehrer@etas.com>,
"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: Thu, 25 Feb 2016 08:43:08 -0600 [thread overview]
Message-ID: <20160225144308.GG9598@jcartwri.amer.corp.natinst.com> (raw)
In-Reply-To: <20160225141806.GB16161@linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 772 bytes --]
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?
Josh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-02-25 14:43 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 [this message]
2016-02-26 10:53 ` Mathias Koehrer
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=20160225144308.GG9598@jcartwri.amer.corp.natinst.com \
--to=joshc@ni.com \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=mathias.koehrer@etas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.