[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200604131627.GC4117@hirez.programming.kicks-ass.net>
Date: Thu, 4 Jun 2020 15:16:27 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Frederic Weisbecker <frederic@...nel.org>
Cc: Ingo Molnar <mingo@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>,
Christoph Lameter <cl@...ux.com>,
Chris Friesen <chris.friesen@...driver.com>,
Marcelo Tosatti <mtosatti@...hat.com>,
Jim Somerville <Jim.Somerville@...driver.com>
Subject: Re: [PATCH 0/2] sched/isolation: Isolate unbound kthreads
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!
Powered by blists - more mailing lists