> If we have no threads this is not a problem. So can you explain to me
> where the threads are in this example? I'm too dense to get your
> telegraphy, have some pity.
Assuming we queue signals to arbitary threads then a single thread causing all
the open/close/read events would queue open/close/read events onto arbitary
signal queues. So thread 1 might see open open and thread 2 see close read-ready
> Of course, you are violating POSIX, but only for a process that expects
> to get non-POSIX semantics. Ordinary processes don't see this.
But they can trigger it too. The signal to all members case for a couple of
specific cases is the one thats cheap to evaluate and handle
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Aug 31 2000 - 21:00:14 EST