Messages in this thread | | | Date | Fri, 26 Jun 1998 07:26:58 +0200 (MET DST) | From | MOLNAR Ingo <> | Subject | Re: Thread implementations... |
| |
On Thu, 25 Jun 1998 robey@lag.net wrote:
[...] > One a side note, signals don't tend to work for large-scale projects > because there are only N signals. If several libraries need to do > async I/O using signals, they would have to coordinate somehow to > pick which signal each will use in place of SIGIO... and that's > assuming we have the option of choosing another signal besides > SIGIO (do we? or does Linux only support SIGIO for this?)
the 32 signals limit is gone. Linux 2.1 has a new signal implementation, with 64 signals right now, but it can be extended to any larger number if needed. glibc already uses a new signal (not USR1) to do the thread stuff.
-- mingo
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |