On Tue, 1 May 2001, Jan Mikkelsen wrote:
> Mike Silbersack <[EMAIL PROTECTED]> wrote:
> [ On using aio on disks vs. sockets ]
> >Sockets already support non-blocking IO, and have for a long while.
> >Hence, the socket code is probably more optimized for non-blocking
> >operation than AIO operation. As a plus, using non-blocking socket
> >operations will allow your code to run on any platform; aio isn't as
> >portable.
>
> I recall reading about possible zero copy I/O using the aio interface. Is
> anyone thinking about this? And on a related note, how about something like
> IRIX's O_DIRECT mode for files?
>
> I'm sure there are lots of issues, but I'm curious.
>
> Jan Mikkelsen
I think the zero-copy patch for FreeBSD sets the page of the written COW
and can thereby work with the standard write call. (Assuming that you
don't re-write the page soon after doing the write.)
Mike "Silby" Silbersack
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
