From owner-freebsd-current Wed Jul 31 11:39:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA15718 for current-outgoing; Wed, 31 Jul 1996 11:39:18 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA15713 for ; Wed, 31 Jul 1996 11:39:16 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA02488; Wed, 31 Jul 1996 11:38:39 -0700 From: Terry Lambert Message-Id: <199607311838.LAA02488@phaeton.artisoft.com> Subject: Re: Using clustered writes for NFSv3 To: dfr@render.com (Doug Rabson) Date: Wed, 31 Jul 1996 11:38:39 -0700 (MST) Cc: current@FreeBSD.ORG In-Reply-To: from "Doug Rabson" at Jul 23, 96 02:13:45 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > 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! PLEASE someone, commit this change! Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.