[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b88327780661496fbee6d8ebe2e0d965@AcuMS.aculab.com>
Date: Wed, 25 Mar 2020 18:05:27 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Marcelo Tosatti' <mtosatti@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>
CC: Chris Friesen <chris.friesen@...driver.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Christoph Lameter" <cl@...ux.com>,
Jim Somerville <Jim.Somerville@...driver.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Peter Zijlstra <peterz@...radead.org>
Subject: RE: [PATCH v2] isolcpus: affine kernel threads to specified cpumask
From: Marcelo Tosatti
> Sent: 24 March 2020 15:20
>
> This is a kernel enhancement to configure the cpu affinity of kernel
> threads via kernel boot option isolcpus=no_kthreads,<isolcpus_params>,<cpulist>
>
> When this option is specified, the cpumask is immediately applied upon
> thread launch. This does not affect kernel threads that specify cpu
> and node.
>
> This allows CPU isolation (that is not allowing certain threads
> to execute on certain CPUs) without using the isolcpus=domain parameter,
> making it possible to enable load balancing on such CPUs
> during runtime
...
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??
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
Powered by blists - more mailing lists