Messages in this thread | | | Date | Tue, 21 May 2002 16:21:38 -0500 | From | Dave McCracken <> | Subject | Re: [RFC] POSIX personality |
| |
--On Tuesday, May 21, 2002 02:13:01 PM -0700 george anzinger <george@mvista.com> wrote:
> What you are proposing seem a bit vague. I think that > CLONE_THREAD should group all the thread related stuff under > the one flag. IMHO POSIX compatibility should not be off in > the corner as a step child, but rather should be the norm. > The CLONE_THREAD flag would indicate to fork that it should > create a POSIX thread and set up the needed shared stuff. I > rather image this to be a structure that each task_struct > points to, possibly with a usage count (but that is a > detail). Each thread_struct would point to such a > structure, but processes that are not threaded would not be > sharing this area with other threads.
That's a possibility I've considered, but I gather most of the kernel community would prefer to see each resource have its own flag to clone() so applications can pick and choose which ones to share. I'm guessing that in most cases multithreaded apps will choose all flags.
Dave McCracken
====================================================================== Dave McCracken IBM Linux Base Kernel Team 1-512-838-3059 dmccr@us.ibm.com T/L 678-3059
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |