From owner-freebsd-hackers Fri May 7 18:30:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mailer.syr.edu (mailer.syr.edu [128.230.18.29]) by hub.freebsd.org (Postfix) with ESMTP id 2506214CE0 for ; Fri, 7 May 1999 18:30:32 -0700 (PDT) (envelope-from cmsedore@mailbox.syr.edu) Received: from rodan.syr.edu by mailer.syr.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.D953CD40@mailer.syr.edu>; Fri, 7 May 1999 21:30:37 -0400 Received: from localhost (cmsedore@localhost) by rodan.syr.edu (8.8.7/8.8.7) with SMTP id VAA26382; Fri, 7 May 1999 21:30:32 -0400 (EDT) X-Authentication-Warning: rodan.syr.edu: cmsedore owned process doing -bs Date: Fri, 7 May 1999 21:30:32 -0400 (EDT) From: Christopher Sedore X-Sender: cmsedore@rodan.syr.edu To: Julian Elischer Cc: hackers@FreeBSD.ORG Subject: Re: aio patches available In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 May 1999, Julian Elischer wrote: > > > On Fri, 7 May 1999, Christopher Sedore wrote: > > > > > I've bundled up my patches and made them available at > > http://tfeed.maxwell.syr.edu/aio_diffs.tgz > > > > As the Aio stuff is supposed to be posix inspired, a comment on the > standards compiance of these features might be in order.. WRT aio_waitcomplete, as far as I know its not part of the spec, so doesn't affect compliance. IMHO, its sorely needed though. The rest of the modifications are performance enhancements or a bug fix, and don't change the behavior of the function calls except to be more efficient. With the implementation in -current now, if you queued 32 reads on sockets, no other aio operations (except physio) would do anything until one of the socket reads completed. Seems like a recipe for problems of various kinds if you didn't know this. Is there a web-downloadable spec available? Do I need to buy a book? A pointer would be appreciated. -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message