OpenVZ Forum


Home » Mailing lists » Devel » [RFC][PATCH] Add child reaper to struct pspace
Re: [RFC][PATCH] Add child reaper to struct pspace [message #16629 is a reply to message #16594] Fri, 08 September 2006 14:02 Go to previous messageGo to previous message
ebiederm is currently offline  ebiederm
Messages: 1354
Registered: February 2006
Senior Member
"Serge E. Hallyn" <serue@us.ibm.com> writes:

> Quoting Eric W. Biederman (ebiederm@xmission.com):
>> Yes.  We all so need something like that list to support kill -1.
>> Although walking the list of all processes may be sufficient for a first
>> pass.
>> 
>> The real trick is handing nested pid namespaces, properly.
>
> Not if, as you've suggested in the past, pid_ns 5 has valid pids in its
> own pid_ns for every process in pid_namespaces nested under it.
>
> It should be simple to implement, should not impact the non-container
> cases, and should only start to impact performance as the nesting gets
> deep, which AFAIK we all believe won't happen (max nesting of 2 AFAICS,
> one checkpointable application container under one vserver-thingie)
>
> And it makes kill -1 trivial, as in pid_ns 5 we just kill all processes
> in pid_ns 5, without worrying about finding the ones in it's decendent
> pid namespaces.

If you do it correctly I agree.  But you have to be very careful where
you put the list.  

My point being not that we can't get this correct with simple code, but
that it is easy to get it wrong.

Eric
_______________________________________________
Containers mailing list
Containers@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/containers
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: Re: [RFC][PATCH] Rename pspace to pid_namespace
Next Topic: Re: [RFC][PATCH 1/2] add user namespace [try #2]
Goto Forum:
  


Current Time: Sun Jul 20 23:15:39 GMT 2025

Total time taken to generate the page: 0.08271 seconds