Date: Sun, 3 Aug 1997 13:43:22 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: gpalmer@FreeBSD.ORG (Gary Palmer) Cc: dyson@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: non-blocking file i/o Message-ID: <199708032043.NAA02183@phaeton.artisoft.com> In-Reply-To: <22934.870566300@orion.webspan.net> from "Gary Palmer" at Aug 2, 97 07:58:20 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > The AIO code is a standard (nice) way to implement database I/O. > > Will it allow the write() to complete more quickly and actually be > async, or just provide a callback to the program when the OS finally > commits the data to disk? For INN's DBZ, I don't think the callback > matters at all. The time it takes to do the write() is what is > important in this case. It should allow the write to be queued. You will have to wait for completion to verify that it actually took place. Async I/O is a concurrency boost, if your software is correctly written. If your software is not correctly written, then you will sit in an aiowait() waiting for the write completion, instead of queueing the next write, like you should be doing. Exactly what do you think an asynchronous wrute should do, if not queue the write for servicing, and return immediately? Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199708032043.NAA02183>