From: Peter Zijlstra <peterz@infradead.org>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <cl@linux.com>,
Chris Friesen <chris.friesen@windriver.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Jim Somerville <Jim.Somerville@windriver.com>
Subject: Re: [PATCH 0/2] sched/isolation: Isolate unbound kthreads
Date: Thu, 4 Jun 2020 15:16:27 +0200 [thread overview]
Message-ID: <20200604131627.GC4117@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20200527142909.23372-1-frederic@kernel.org>
On Wed, May 27, 2020 at 04:29:07PM +0200, Frederic Weisbecker wrote:
> Kthreads are harder to affine and isolate than user tasks. They can't
> be placed inside cgroups/cpusets and the affinity for any newly
> created kthread is always overriden from the inherited kthreadd's
> affinity to system wide. Take that into account for nohz_full.
>
Thanks!
prev parent reply other threads:[~2020-06-04 13:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 14:29 [PATCH 0/2] sched/isolation: Isolate unbound kthreads Frederic Weisbecker
2020-05-27 14:29 ` [PATCH 1/2] kthread: Switch to cpu_possible_mask Frederic Weisbecker
2020-06-16 12:21 ` [tip: sched/core] " tip-bot2 for Marcelo Tosatti
2020-05-27 14:29 ` [PATCH 2/2] isolcpus: Affine unbound kernel threads to housekeeping cpus Frederic Weisbecker
2020-06-16 12:21 ` [tip: sched/core] " tip-bot2 for Marcelo Tosatti
2020-06-04 13:16 ` Peter Zijlstra [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=20200604131627.GC4117@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Jim.Somerville@windriver.com \
--cc=akpm@linux-foundation.org \
--cc=chris.friesen@windriver.com \
--cc=cl@linux.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mtosatti@redhat.com \
--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 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).