From owner-cvs-src@FreeBSD.ORG Sun Jun 12 08:08:34 2005 Return-Path: X-Original-To: cvs-src@freebsd.org Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FFD316A41C; Sun, 12 Jun 2005 08:08:34 +0000 (GMT) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FF0243D1F; Sun, 12 Jun 2005 08:08:34 +0000 (GMT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id ED4745CACA; Sun, 12 Jun 2005 01:08:33 -0700 (PDT) Date: Sun, 12 Jun 2005 01:08:33 -0700 From: Alfred Perlstein To: Brian Fundakowski Feldman Message-ID: <20050612080833.GJ17867@elvis.mu.org> References: <200506102350.j5ANofFM008212@repoman.freebsd.org> <20050611034930.GY17867@elvis.mu.org> <20050611064956.GC66188@green.homeunix.org> <20050611141021.GD17867@elvis.mu.org> <20050611170425.GD66188@green.homeunix.org> <20050611174617.GE17867@elvis.mu.org> <20050611212534.GE66188@green.homeunix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050611212534.GE66188@green.homeunix.org> User-Agent: Mutt/1.4.2.1i Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/nfsclient nfs_bio.c nfs_vfsops.c nfsargs.h nfsmount.h src/sys/sys buf.h bufobj.h src/sys/kern vfs_bio.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Jun 2005 08:08:34 -0000 * Brian Fundakowski Feldman [050611 14:25] wrote: > On Sat, Jun 11, 2005 at 10:46:17AM -0700, Alfred Perlstein wrote: > > * Brian Fundakowski Feldman [050611 10:04] wrote: > > > > > > Well, the easy solution is just fsync(2) :) This change jibes with > > > Terry's explanation (thanks, Juli). It would be good to implement > > > the rest of the functionality for non-blocking NFS client, too, but I > > > think that can be dne gradually over time. > > > > lol. > > FWIW, I was aware of Terry's explanation, I just consider it bunk. > > Heh. Well, we can always throw things under a kernel option. I never > saw Terry's e-mail on the topic until just now -- my understanding was > that this was generally the Right Thing To Do after spending a while > reading POSIX/SUS (due to gad pointing out that it was definitely a > bad idea to just return short writes). Seriously, have you tested what happens to a libc_r app that opens an nfs file F_SYNC? My guess is that it's not pretty. -- - Alfred Perlstein - email: bright@mu.org cell: 408-480-4684