Re: init's children list is long and slows reaping children.

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Ingo Molnar
Date: Friday, April 6, 2007 - 12:43 pm

* Oleg Nesterov <oleg@tv-sign.ru> wrote:



this isnt a kernel-thread special case. The right solution IMO is to 
first migrate wait4()'s ->children use over to a new p->exiting_children 
list and then to gradually get rid of all remaining uses of p->children. 
(the first patch of which i sent a few minutes ago)

that way wait4() will be sped up, and quite dramatically i believe. No 
need to deal with kthreads here at all - those just wont ever show up in 
the ->exiting_children list. Am i missing something?

	Ingo
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: init's children list is long and slows reaping children., Eric W. Biederman, (Fri Apr 6, 2:10 am)
Re: init's children list is long and slows reaping children., Eric W. Biederman, (Fri Apr 6, 8:45 am)
Re: init's children list is long and slows reaping children., Eric W. Biederman, (Fri Apr 6, 10:34 am)
Re: init's children list is long and slows reaping children., Eric W. Biederman, (Fri Apr 6, 12:15 pm)
Re: init's children list is long and slows reaping children., Ingo Molnar, (Fri Apr 6, 12:43 pm)
Re: init's children list is long and slows reaping children., Eric W. Biederman, (Fri Apr 6, 12:59 pm)
Re: init's children list is long and slows reaping children., Jeremy Fitzhardinge, (Fri Apr 6, 2:04 pm)
Re: init's children list is long and slows reaping children., Eric W. Biederman, (Sat Apr 7, 5:38 pm)