[<prev] [next>] [day] [month] [year] [list]
Message-Id: <1157380674.3895.55.camel@frecb000686>
Date: Mon, 04 Sep 2006 16:37:54 +0200
From: Sébastien Dugué <sebastien.dugue@...l.net>
To: Jakub Jelinek <jakub@...hat.com>
Cc: Ulrich Drepper <drepper@...hat.com>, suparna@...ibm.com,
Badari Pulavarty <pbadari@...ibm.com>,
Zach Brown <zach.brown@...cle.com>,
Christoph Hellwig <hch@...radead.org>,
Evgeniy Polyakov <johnpol@....mipt.ru>,
lkml <linux-kernel@...r.kernel.org>,
David Miller <davem@...emloft.net>,
netdev <netdev@...r.kernel.org>, linux-aio@...ck.org
Subject: Re: Kernel patches enabling better POSIX AIO (Was Re: [3/4]
kevent: AIO, aio_sendfile)
On Sat, 2006-08-12 at 15:28 -0400, Jakub Jelinek wrote:
> 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.
>
That's exactly what is done in libposix-aio.
Sébastien.
--
-----------------------------------------------------
Sébastien Dugué BULL/FREC:B1-247
phone: (+33) 476 29 77 70 Bullcom: 229-7770
mailto:sebastien.dugue@...l.net
Linux POSIX AIO: http://www.bullopensource.org/posix
http://sourceforge.net/projects/paiol
-----------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists