Date: Tue, 1 May 2001 09:55:41 +1000 From: "Jan Mikkelsen" <janm@transactionware.com> To: "Freebsd-Hackers" <freebsd-hackers@FreeBSD.ORG> Subject: Re: write() vs aio_write() Message-ID: <00bd01c0d1d1$106ccdf0$0901a8c0@haym.transactionsite.com>
next in thread | raw e-mail | index | archive | help
Mike Silbersack <silby@silby.com> 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00bd01c0d1d1$106ccdf0$0901a8c0>