From owner-freebsd-arch Sun Mar 2 10:53:33 2003 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB86637B401 for ; Sun, 2 Mar 2003 10:53:32 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62DC843F75 for ; Sun, 2 Mar 2003 10:53:32 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by canning.wemm.org (Postfix) with ESMTP id 4D54B2A89E; Sun, 2 Mar 2003 10:53:32 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: "Alan L. Cox" Cc: arch@freebsd.org Subject: Re: Removal of ENABLE_VFS_IOOPT In-Reply-To: <3E619B26.DF1E4FC7@imimic.com> Date: Sun, 02 Mar 2003 10:53:32 -0800 From: Peter Wemm Message-Id: <20030302185332.4D54B2A89E@canning.wemm.org> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Alan L. Cox" wrote: > Before I begin work on vm_object locking, I'd like to remove > ENABLE_VFS_IOOPT from the kernel sources. ENABLE_VFS_IOOPT was a > work-in-progress by John Dyson to perform zero-copy file system I/O. > Unfortunately, it still has some unresolved issues, and no one has taken > an active interest in fixing them. Hold on a second.. I thought the zero-copy folks fixed this up and it is required for turning on zero-copy mode etc. I remember they added code to fix the read() coherency problems. Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message