Date: Mon, 30 Apr 2001 13:11:03 -0500 (CDT) From: Mike Silbersack <silby@silby.com> To: Charles Randall <crandall@matchlogic.com> Cc: 'Alfred Perlstein' <bright@wintelcom.net>, =?iso-8859-1?Q?=AAL=AD=5E?= =?iso-8859-1?Q?=B6W?= <r88074@csie.ntu.edu.tw>, Freebsd-Hackers <freebsd-hackers@FreeBSD.ORG> Subject: RE: write() vs aio_write() Message-ID: <Pine.BSF.4.31.0104301309200.20550-100000@achilles.silby.com> In-Reply-To: <5FE9B713CCCDD311A03400508B8B30130828EC88@bdr-xcln.corp.matchlogic.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 30 Apr 2001, Charles Randall wrote: > Regarding aio_*, Alfred Perlstein writes: > >It's a good idea to use it for disk IO, probably not a good > >idea for network IO. > > Could you elaborate? > > -Charles 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. Mike "Silby" Silbersack 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?Pine.BSF.4.31.0104301309200.20550-100000>