On Wed, Jan 23, 2013 at 06:22:24PM +0400, Konstantin Osipov
wrote:
> libeio manual says that:
Thanks, this is another doc bug.
> In my view, it's important to make sure the callback is always,
> otherwise it's hard to reliably manage resources associated
> with eio function arguments.
I am no
On Wed, Jan 23, 2013 at 06:11:20PM +0400, Konstantin Osipov
wrote:
> * Marc Lehmann [13/01/23 17:50]:
> > Note also that the solution to having your own threadpool is simply...
> > having your own threadpool.
>
> Forking libeio is and (has always been with free software)
> an obvious option.
C
Hello,
libeio manual says that:
--quote
Even if cancelled, the finish callback will still be invoked - the callbacks
of all cancellable requests need to check whether the request has been
cancelled by calling EIO_CANCELLED (req):
--end quote
Yet in the implementation does not do this
(http://cvs
* Marc Lehmann [13/01/23 17:50]:
> Note also that the solution to having your own threadpool is simply...
> having your own threadpool.
Forking libeio is and (has always been with free software)
an obvious option.
I'm immensely thankful to you for libeio - it has already saved us
a lot of time, a
