Messages in this thread | | | Subject | Re: SCO: "thread creation is about a thousand times faster than on | Date | Tue, 29 Aug 2000 16:09:31 +0100 | From | David Howells <> |
| |
Would it be possible to make fork() or clone() from a process whose tgid!=pid reparent the child to the thread group leader automatically? Thus, when the creating thread goes away, the child is still a child of the "process", and SIGCHLD is still going to go to the process (leader thread).
Also all child "processes" and "threads" are then logically children of the "process", given that a "process" is then defined by the tgid.
Also my 2p on the execve() problem: if the master thread does an execve(), there must be a point of no return, at which point all the child threads should be deleted, IMHO, otherwise they turn into full processes in their own right, and the thread-signalling framework goes out the window.
And for a further thought on the subject, is it possible for when a child thread does an execve(), to wangle the master thread into making this call, with all other threads SIGSTOP'd until completion (& death) or failure (& resumption)? (though that's probably better done in userspace)
David Howells - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
| |