Asynchronous I/O under UNIX
Archer Sully
archer at elysium.esd.sgi.com
Thu Dec 28 13:13:05 AEST 1989
In article <20880 at pasteur.Berkeley.EDU>, jas at postgres.uucp (James
Shankland) writes:
> In article <6679 at lynx.UUCP> m5 at lynx.uucp (Mike McNally) writes:
> >peterson at crash.cts.com (John Peterson) writes:
>
> >... in fact, if I had threads, I don't think I'd
> >want or need a separate kernel-supported async I/O mechanism.
>
> Yes! I strongly agree, and it sure is nice to hear someone else taking
> this position. I consider asynchronous I/O a hack to compensate for the
> absence of sufficiently lightweight processes. Of course, one person's
> spartan elegance is another's semantic impoverishment, but I consider
> it a cleaner, clearer programming model.
>
> jas
I've done this on IRIX (Silicon Graphics hacks....er IMPROVEMENTS to
SYSV :-), and it works ok. Benefit turns out to be highly dependant
on exactly what you are doing, and there are, of course, lots of funky
limitations, but it does work.
If anyone wants it I may even be able to dig it up.
Archer Sully | A Mind is a Terrible thing to Taste
(archer at sgi.com) | - Ministry
More information about the Comp.unix.wizards
mailing list