From owner-freebsd-hackers Sat Aug 2 16:58:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA22870 for hackers-outgoing; Sat, 2 Aug 1997 16:58:28 -0700 (PDT) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA22865; Sat, 2 Aug 1997 16:58:22 -0700 (PDT) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with ESMTP id TAA06388; Sat, 2 Aug 1997 19:58:21 -0400 (EDT) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (WEBSPAN/970608) with ESMTP id TAA22936; Sat, 2 Aug 1997 19:58:21 -0400 (EDT) To: dyson@FreeBSD.ORG cc: hackers@FreeBSD.ORG From: "Gary Palmer" Subject: Re: non-blocking file i/o In-reply-to: Your message of "Sat, 02 Aug 1997 02:07:22 CDT." <199708020707.CAA11836@dyson.iquest.net> Date: Sat, 02 Aug 1997 19:58:20 -0400 Message-ID: <22934.870566300@orion.webspan.net> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "John S. Dyson" wrote in message ID <199708020707.CAA11836@dyson.iquest.net>: > The AIO code is a standard (nice) way to implement database I/O. Will it allow the write() to complete more quickly and actually be async, or just provide a callback to the program when the OS finally commits the data to disk? For INN's DBZ, I don't think the callback matters at all. The time it takes to do the write() is what is important in this case. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info