Re: Async IO

H. Peter Anvin (hpa@transmeta.com)
30 Jan 1997 05:13:40 GMT

Followup to: <m23evo8f0g.fsf@frob.mlm.extern.lrz-muenchen.de>
By author: Andi Kleen <andi@mlm.extern.lrz-muenchen.de>
In newsgroup: linux.dev.kernel
>
> One problem currently is that Linux doesn't have enough signals.
> In practive you can only use SIGUSR1 and SIGUSR2 for your async aio
> stuff and that's usually not enough. Linuxthreads already needs SIGUSR1
> so you can't use it. You'll probably have to wait for full POSIX 1003.1b
> signal support in Linux.
>

We probably should create a couple of more signals... SIGUNUSED (31)
is still available, SIGLOST (29) is commented out, signal number 0 is
unused, and SIGPWR (30) basically only makes sense to init(8). I
would suggest creating a SIGTHREAD reserved for Linuxthreads; that way
it wouldn't have to eat up a user signal...

-hpa

-- 
This space intentionally has nothing but text explaining why this
space has nothing but text explaining that this space would otherwise
have been left blank, and would otherwise have been left blank.