> A thread library - maybe not. But the SETTID thing makes sense even for
> a fork() user to avoid the fork/SIGCHLD race condition. In contrast, a
> CLRTID does _not_ make sense in that situation, so I actually think they
> are two separate issues (and should thus be two separate bits).
okay. And it also makes sense for a newly forked task to know (and cache)
its own PID, without having to call getpid() again.
Ingo
-
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/