[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130913140422.GE4844@somewhere>
Date: Fri, 13 Sep 2013 16:04:24 +0200
From: Frederic Weisbecker <fweisbec@...il.com>
To: Christoph Lameter <cl@...ux.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Gilad Ben-Yossef <gilad@...yossef.com>,
Thomas Gleixner <tglx@...utronix.de>,
Mike Frysinger <vapier@...too.org>,
linux-kernel@...r.kernel.org,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...nel.org>
Subject: Re: [RFC] Restrict kernel spawning of threads to a specified set of
cpus.
On Fri, Sep 13, 2013 at 01:45:55PM +0000, Christoph Lameter wrote:
> On Thu, 12 Sep 2013, Frederic Weisbecker wrote:
>
> > So yeah it's a problem in theory. Now in practice, I have yet to be convinced because
> > this should be solved after a few iterations in /proc in most cases.
>
> I have seen some drivers regularly spawning threads all over the machnine.
> This is a practical issue that I am addresing.
> >
> > Now the issue doesn't only concern kthreads but all tasks in the system.
> > If we really want to solve that race, then may be we can think of a kernel_parameter
> > that sets the initial affinity of init and then lets get it naturally inherited
> > through the whole tree.
>
> This patch that we are discussing does exactly that.
>
Indeed, I just looked that again and your cpu_kthread_mask actually also applies to init.
cpu_init_mask would be a better name I think.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists