From owner-freebsd-current Wed Mar 22 12:38:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mg134-217.ricochet.net [204.179.134.217]) by hub.freebsd.org (Postfix) with ESMTP id 1EB4A37C24E; Wed, 22 Mar 2000 12:38:32 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA00661; Wed, 22 Mar 2000 12:39:46 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003222039.MAA00661@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Dillon Cc: Paul Richards , Richard Wendland , Alfred Perlstein , Poul-Henning Kamp , current@FreeBSD.ORG, fs@FreeBSD.ORG Subject: Re: FreeBSD random I/O performance issues In-reply-to: Your message of "Tue, 21 Mar 2000 22:17:52 PST." <200003220617.WAA86154@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 22 Mar 2000 12:39:42 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > effects of the I/O being in-progress. If a user program doesn't access > any of the information it recently wrote the whole mechanism winds up > operating asynchronously in the background. If a user program does, > then the write behind mechanism breaks down and you get a stall. What makes no sense is that it should be perfectly ok to _read_ this information back. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message