Date: Mon, 1 Dec 1997 15:14:12 -0700 From: Nate Williams <nate@mt.sri.com> To: "John S. Dyson" <toor@dyson.iquest.net> Cc: nate@mt.sri.com (Nate Williams), current@FreeBSD.ORG Subject: Re: FYI: usage of new AIO calls Message-ID: <199712012214.PAA12892@mt.sri.com> In-Reply-To: <199712012202.RAA07400@dyson.iquest.net> References: <199712012154.OAA12784@mt.sri.com> <199712012202.RAA07400@dyson.iquest.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> > One more question. AIO == Asynchronous I/O, but LIO? > > > AIO == Asynchronous I/O. > LIO == List (directed) I/O. > > LIO essentially allows for multiple AIO requests to be batched into > a single system call. It is kind of like writev/readv, except you > can intermix read and write system calls with LIO. With LIO, you can > specify a signal to post when it is fully done. signanosleep(2) is > especially useful in conjunction with LIO. Cool, but it sounds pretty complicated to keep straight. I suppose it's a bit more effecient than multiple AIO calls, but I'd be the type that would do multiple calls at first just because my head would get all screwed up if I tried making LIO effecient. :) Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199712012214.PAA12892>