[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.01.0909181632500.4950@localhost.localdomain>
Date: Fri, 18 Sep 2009 16:38:33 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Oleg Nesterov <oleg@...hat.com>
cc: Wu Fei <at.wufei@...il.com>, Ingo Molnar <mingo@...e.hu>,
"Eric W. Biederman" <ebiederm@...ssion.com>, arjan@...radead.org,
jeremy@...p.org, mschmidt@...hat.com, mingo@...hat.com,
hpa@...or.com, linux-kernel@...r.kernel.org, tj@...nel.org,
tglx@...utronix.de, Andrew Morton <akpm@...ux-foundation.org>,
linux-tip-commits@...r.kernel.org,
Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: [PATCH 0/1] kthreads: simplify !kthreadd_task logic, kill
kthreadd_task_init_done
On Sat, 19 Sep 2009, Oleg Nesterov wrote:
>
> On 09/18, Linus Torvalds wrote:
> >
> > As to why pid == 0 wouldn't work, I don't know, but I'll take your word
> > for it.
>
> Say, admin wants to renice kthreadd or change its affinity. And we can't
> show kthread in /proc if its pid is 0.
Ok, so it's a "that's not good" kind of situation, rather than a "it
wouldn't work" one. Fair enough.
Of course, another way to do this would be to simply use CLONE_STOPPED to
create the 'init' task first, but not wake it up - and then wake it up
only after kthreadd exists.
I'm sure there are other things we could do ;)
Linus
--
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