On Tue, Aug 23, 2005 at 05:56:09AM -0400, Jakub Jelinek wrote: > POSIX AIO needs to handle SIGEV_NONE, SIGEV_SIGNAL and SIGEV_THREAD > notification. Obviously kernel shouldn't create threads for SIGEV_THREAD > itself, as kernel shouldn't hardcode all the implementation details how a > thread can be created. But it would be good if AIO signalling e.g. handled > both SIGEV_SIGNAL and SIGEV_SIGNAL | SIGEV_THREAD_ID, with the same usage as > e.g. timer_* syscalls. If kernel makes sure SI_ASYNCIO si_code is set in > the notification signal siginfos, glibc could even use just one helper > thread for timer_*/[al]io_* and maybe in the future other SIGEV_THREAD > notification.
The signal patch from Sebastien should handle the SIGEV_foo. The patch at http://www.kvack.org/~bcrl/patches/aio-2.6.13-rc6-B1/817_sigevent.diff has the latest changes from me and should do what is needed. -ben - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/