> >There is no need to store pending signals. It will be impossible
> >to achieve in a multi-threaded perl runtime.
> 
> No, it won't be that tough to get multiple pending signals for a thread. 
> Not "real" Unix signals, perhaps, but what look like them, more or less.
If 
> several alarms time out essentially simultaneously, or some I/Os finish at

> the same time, a thread could have a stack of things to look at.

Suppose we are talking about real unix signals. Otherwise, we can use event
loop for sending/processing event to do so.

Since the kernel already has signal queue, we can take advantage of it by 
using sigwaitinfo(). We should limit normal signal handler for error
handling only. That will make system design simpler.

Hong

Reply via email to