Date: Wed, 20 Apr 2005 16:38:42 +0200 From: Marc Olzheim <marcolz@stack.nl> To: Brian Fundakowski Feldman <green@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: NFS client/buffer cache deadlock Message-ID: <20050420143842.GB77731@stack.nl> In-Reply-To: <20050420142448.GH1157@green.homeunix.org> References: <20050418202213.GC1157@green.homeunix.org> <20050418203321.GA88774@stack.nl> <20050419133227.GA11612@stack.nl> <20050419151800.GE1157@green.homeunix.org> <20050419160258.GA12287@stack.nl> <20050419160900.GB12287@stack.nl> <20050419161616.GF1157@green.homeunix.org> <20050419204723.GG1157@green.homeunix.org> <20050420140409.GA77731@stack.nl> <20050420142448.GH1157@green.homeunix.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Wed, Apr 20, 2005 at 10:24:48AM -0400, Brian Fundakowski Feldman wrote: > > It does and it seems to work. The NFS performance drops considerably > > though, from 8/9 MByte/s to 3/4 on sequential reads for instance. > > > > kern/79208 is fixed by this indeed, in that I get short writes (in case > > of my test server at 1802240+ bytes, so './writev 2 foo' fails... > > Performance drops in what cases? Hmm, seems only to happen in large sequential reads... It might just be the FreeBSD 4.6 NFS server that is the problem though. I've had more NFS troubles with it. Btw.: I'm not sure write(),writev() and pwrite() are allowed to do short writes on regular files... ? Marc [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCZmlyezjnobFOgrERAshmAJ45uor6Jz6tuOrKt20hozLTMDnPbACePn+5 ZE3M6Au5bLATSF+rP5JuuIY= =ufVf -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050420143842.GB77731>