On Sat, Aug 12, 2006 at 12:10:35PM -0700, Ulrich Drepper wrote:
> > I am wondering about that too. IIRC, the IO_NOTIFY_* constants are not
> > part of the ABI, but only internal to the kernel implementation. I think
> > Zach had suggested inferring THREAD_ID notification if the pid specified
> > is not zero. But, I don't see why ->sigev_notify couldn't used directly
> > (just like the POSIX timers code does) thus doing away with the
> > new constants altogether. Sebestian/Laurent, do you recall?
>
> I suggest to model the implementation after the timer code which does
> exactly what we need.
Yeah, and if at all possible we want to use just one helper thread for
SIGEV_THREAD notification of timers/aio/etc., so it really should behave the
same as timer thread notification.
Jakub
-
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/
- References:
- Re: [3/4] kevent: AIO, aio_sendfile() implementation.
- Re: [3/4] kevent: AIO, aio_sendfile() implementation.
- Re: [3/4] kevent: AIO, aio_sendfile() implementation.
- Re: [3/4] kevent: AIO, aio_sendfile() implementation.
- Re: [3/4] kevent: AIO, aio_sendfile() implementation.
- Re: [3/4] kevent: AIO, aio_sendfile() implementation.
- Re: [3/4] kevent: AIO, aio_sendfile() implementation.
- Re: [3/4] kevent: AIO, aio_sendfile() implementation.
- Kernel patches enabling better POSIX AIO (Was Re: [3/4] kevent: AIO, aio_sendfile)
- Re: Kernel patches enabling better POSIX AIO (Was Re: [3/4] kevent: AIO, aio_sendfile)
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]