1:N threading

[Terry Lambert]

Daniel Eischen wrote:
> Libc_r will go bye-bye.  The KSE library will give you 1:N
> as long as you don't use pthread_setconcurrency() and don't
> create any PTHREAD_SCOPE_PROCESS threads.


I think that maybe you need to get over the "fear factor" here.

Specifically, it's probably time to commit a "libkse", the same
way that Jeff committed a "libthr", so that it doesn't directly
replace "libc_r", and leave people hanging over a cliff if it
has a bug.

Better to take an approach that doesn't piss people off, but gets
the code to a wider audience.

Is this a possibility?  The only thing that seems screwed up is
the signals processing.  Jeff's code panic's the system with a
lock order reversal on exit processing, under some circumstances,
but it's tolerated because it didn't outright replace "libc_r",
and offer an alternative to "conservative" -CURRENT users.

-- Terry