From owner-freebsd-current Thu Aug 1 02:57:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA07461 for current-outgoing; Thu, 1 Aug 1996 02:57:03 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA07456 for ; Thu, 1 Aug 1996 02:57:01 -0700 (PDT) Received: from minnow.render.com (minnow.render.com [193.195.178.1]) by minnow.render.com (8.6.12/8.6.9) with SMTP id KAA21109; Thu, 1 Aug 1996 10:50:23 +0100 Date: Thu, 1 Aug 1996 10:50:22 +0100 (BST) From: Doug Rabson To: Terry Lambert cc: current@FreeBSD.ORG Subject: Re: Using clustered writes for NFSv3 In-Reply-To: <199607311838.LAA02488@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 31 Jul 1996, Terry Lambert wrote: > > In NFSv3, when a buffer is written to a server, normally the server > > doesn't write the data to stable storage immediately. Instead, it informs > > the client that the data is written but 'unstable'. The client can later > > commit the data to stable storage in a seperate call. > > [ ... ] > > > By a stroke of luck, the existing code for clustered writes in vfs_bio.c > > and vfs_cluster.c can be made to work for NFSv3 as well. I needed to > > tweak cluster_wbuild a little to copy over the B_NEEDCOMMIT flag and to > > set the b_dirtyoff and b_dirtyend fields of the cluster appropriately. > > Oh, Doug, you stud, you! Oh! I'm blushing! > > PLEASE someone, commit this change! Already done. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939