Re: Non-blocking I/O

Chris Wedgwood (chris@cybernet.co.nz)
Fri, 17 Jul 1998 13:19:48 +1200


> > This really sucks because it means we have to write smarter apps. to put
> > IO like this in another thread or some such and I'm a lazy bastard who
> > would like to be able to avoid having to do this.
>
> So put it in a library _NOT_ the kernel

To be perfectly honest, I'm not really sure how to modify libc/open(3) to do
so correctly and make sure everything still works with regards to signals
and what have you.

I don't even know if its worth it, because I think someone (Gooch?) has
already modified glibc2 so that the aio_* calls already do this.

One thing that might be an issue, but perhaps isn't because clone(2) is
obscenely fast, is that no 'IO threads' will exist on the first call to
open(3) so we have to create them and do the setup, which can take time.

I'm pretty much lost these days on how to make threads applications work
properly with signals anyhow, at one point you needn't a helper thread, now,
I'm not so sure...

-cw

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html