I went thru the POSIX specification and couldn't find any specified limits
regarding this and in most cases these limits are enforced at the library
level. It probably should be left up to the kernel folks to determine the
kernel limits they can live with. The library can adapt to this value. I
don't believe a pthread library would need any "extra" control of how the
signal is delivered. A file descriptor is good enough, seems a waste to
have to provide a sys_call interface.
Regards,
Bill Abt
Senior Software Engineer
Next Generation POSIX Threading for Linux
IBM Cambridge, MA, USA 02142
Ext: +(00)1 617-693-1591
T/L: 693-1591 (M/W/F)
T/L: 253-9938 (T/Th/Eves.)
Cell: +(00)1 617-803-7514
babt@us.ibm.com or abt@us.ibm.com
http://oss.software.ibm.com/developerworks/opensource/pthreads
-
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/