From: Frederic Weisbecker <frederic@kernel.org>
To: Chris Friesen <chris.friesen@windriver.com>
Cc: David Laight <David.Laight@ACULAB.COM>,
'Marcelo Tosatti' <mtosatti@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Christoph Lameter <cl@linux.com>,
Jim Somerville <Jim.Somerville@windriver.com>,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v2] isolcpus: affine kernel threads to specified cpumask
Date: Thu, 26 Mar 2020 17:51:29 +0100 [thread overview]
Message-ID: <20200326165128.GC3946@lenoir> (raw)
In-Reply-To: <76fa0270-40c5-aac7-1c53-38384fa3467d@windriver.com>
On Thu, Mar 26, 2020 at 10:32:51AM -0600, Chris Friesen wrote:
> On 3/26/2020 10:22 AM, Frederic Weisbecker wrote:
> > On Wed, Mar 25, 2020 at 06:05:27PM +0000, David Laight wrote:
>
> > > How about making it possible to change the default affinity
> > > for new kthreads at run time?
> > > Is it possible to change the affinity of existing threads?
> > > Or maybe only those that didn't specify an explicit one??
> >
> > That's already possible yes, most unbound kthreads are accessible
> > through /proc including kthreadd from which new kthread will inherit
> > their CPU affinity.
>
> Are you sure that the new kthread will inherit the CPU affinity?
>
> __kthread_create_on_node() explicitly sets the new thread as SCHED_NORMAL
> with a mask of "cpu_all_mask".
Ah, ok that's the part I missed. What a weird behaviour...
Anyway, I'm working on making all those isolcpus options
controllable through cpusets. So that should be possible at some
future.
prev parent reply other threads:[~2020-03-26 16:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 13:54 [PATCH] affine kernel threads to specified cpumask Marcelo Tosatti
2020-03-23 15:29 ` Chris Friesen
2020-03-24 15:07 ` Marcelo Tosatti
2020-03-23 16:22 ` Thomas Gleixner
2020-03-23 17:02 ` Chris Friesen
2020-03-23 20:31 ` Thomas Gleixner
2020-03-24 11:38 ` Marcelo Tosatti
2020-03-24 15:20 ` [PATCH v2] isolcpus: " Marcelo Tosatti
2020-03-24 15:56 ` Chris Friesen
2020-03-24 16:50 ` Marcelo Tosatti
2020-03-25 0:30 ` Frederic Weisbecker
2020-03-25 11:47 ` Marcelo Tosatti
2020-03-26 16:20 ` Frederic Weisbecker
2020-03-26 16:52 ` Frederic Weisbecker
2020-03-27 12:07 ` Marcelo Tosatti
2020-03-25 18:05 ` David Laight
2020-03-26 11:28 ` Marcelo Tosatti
2020-03-26 16:22 ` Frederic Weisbecker
2020-03-26 16:32 ` Chris Friesen
2020-03-26 16:51 ` Frederic Weisbecker [this message]
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=20200326165128.GC3946@lenoir \
--to=frederic@kernel.org \
--cc=David.Laight@ACULAB.COM \
--cc=Jim.Somerville@windriver.com \
--cc=akpm@linux-foundation.org \
--cc=chris.friesen@windriver.com \
--cc=cl@linux.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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.