* Mathieu Desnoyers: > The related question then becomes: should we issue this system call once > per process, or once per thread at thread creation ? Issuing it once per > thread is marginally more costly for thread creation, but seems to be > easier to deal with internally within the kernel.
I might be missing something, but here is my take: It has to be a per-thread attribute because glibc uses clone internally and wants to set the flag, but the same process may have application or library code which uses clone to create threads, too, but does not know about this new feature. If it's per-process, the existing code would fail. (We may argue indefinitely if this is a supported use case from the glibc point of view, but I'm pretty sure there is code out there which does exactly this, even though it's fairly complicated to get right.) -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
