From owner-freebsd-hackers Mon Apr 30 16:58:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nero.transactionsite.com (nero.transactionsite.com [203.14.245.6]) by hub.freebsd.org (Postfix) with SMTP id 954CD37B423 for ; Mon, 30 Apr 2001 16:58:46 -0700 (PDT) (envelope-from janm@transactionware.com) Received: (qmail 32811 invoked from network); 30 Apr 2001 23:52:01 -0000 Received: from unknown (HELO haym) (192.168.1.9) by 192.168.1.6 with SMTP; 30 Apr 2001 23:52:01 -0000 Message-ID: <00bd01c0d1d1$106ccdf0$0901a8c0@haym.transactionsite.com> From: "Jan Mikkelsen" To: "Freebsd-Hackers" Subject: Re: write() vs aio_write() Date: Tue, 1 May 2001 09:55:41 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3612.1700 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Silbersack 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