Xref: utzoo comp.lang.misc:5429 comp.unix.wizards:23716
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!asuvax!mcdphx!mcdchg!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.lang.misc,comp.unix.wizards
Subject: Re: UNIX does *not* fully support asynchronous I/O
Message-ID: <1990Aug29.155253.18634@chinet.chi.il.us>
Date: 29 Aug 90 15:52:53 GMT
References: <11576:Aug2503:18:3790@kramden.acf.nyu.edu> <1990Aug27.223445.4474@sco.COM> <29639:Aug2903:48:4290@kramden.acf.nyu.edu>
Distribution: usa
Organization: Chinet - Chicago Public Access UNIX
Lines: 11

In article <29639:Aug2903:48:4290@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:

>I was describing how asynchronous I/O works when there's no OS in the
>way. You start talking about how a particular OS does asynchronous I/O.

Does this have something to do with unix?  The usual concept of unix I/O
is that something that is written to disk is likely to be read back and
thus should live in the common buffer pool for a while.  

Les Mikesell
  les@chinet.chi.il.us