Cedric Le Goater <[EMAIL PROTECTED]> writes: >>> what about a kthread that would be spawned when a task is cloned in an >>> unshared pid namespace ? This is an extra cost in term of tasks. >> >> If you use kernel_thread this can happen. (Die kernel_thread). >> If you use the kthread interface keventd will be the parent process and >> we won't have problems. > > so is it something acceptable for mainline ? I think openvz has such > a thread doing the reaping.
Please clarify. Is what acceptable for mainline? >> Thus most users of kernel_thread need to be fixed to use the kthread >> interface. >> >> Thanks for the reminder of this one, I had forgotten that bit of >> reasoning for updating kernel_thread users. > > there are not much left. see below a quick and dirty survey on > 2.6.21-rc4-mm1. Yep. We are almost there. Of course with nfs still pending we have some of the nastier ones left. A couple of the ones in arch/ and kernel/ we don't have to worry about because they are either started early enough it doesn't matter or they implement kthread... Eric _______________________________________________ Containers mailing list [EMAIL PROTECTED] https://lists.linux-foundation.org/mailman/listinfo/containers _______________________________________________ Devel mailing list Devel@openvz.org https://openvz.org/mailman/listinfo/devel
