Messages in this thread | | | From | (Linus Torvalds) | Subject | Re: kernel thread support - LWP's | Date | 19 Jul 1999 01:45:18 GMT |
| |
In article <Pine.SOL.4.05.9907172226570.25819-100000@csa.cs.technion.ac.il>, Alon Ziv <alonz@cs.Technion.AC.IL> wrote: > >I remember someone (David Wragg <dpw@doc.ic.ac.uk>) once mentioned another >new flag idea: a CLONE_SIBLING flag, which will mean that if the new >thread does a clone() the new thread will get the same ppid of the parent. >This (together with the redefinition of the manager thread, above) will >mean that all of the threads report directly to the manager, and any >thread may create another thread _without_ communicating to the manager >(it just creates a new sibling).
This sounds like a Good Idea(tm).
It's also a lot more straightforward as a concept than is the notion of CLONE_PID, which never got really implemented because it has a ton of subtle issues (I think that CLONE_PID will basically always just remain useful for the initial kernel threads, and what pthreads needs in addition to the CLONE_SIBLING flag is a CLONE_SIGNALS thing).
Linus
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |