Date: Wed, 5 Jan 2011 07:57:07 -0500 From: John Baldwin <jhb@freebsd.org> To: freebsd-stable@freebsd.org Cc: jyavenard@gmail.com, marek_sal@wp.pl, perryh@pluto.rain.com, milu@dat.pl, rmacklem@uoguelph.ca Subject: Re: NFSv4 - how to set up at FreeBSD 8.1 ? Message-ID: <201101050757.08116.jhb@freebsd.org> In-Reply-To: <4d244e39.KoPcOoMaWed%2BH5De%perryh@pluto.rain.com> References: <1036681015.111502.1294189339355.JavaMail.root@erie.cs.uoguelph.ca> <4d244e39.KoPcOoMaWed%2BH5De%perryh@pluto.rain.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, January 05, 2011 5:55:53 am perryh@pluto.rain.com wrote: > Rick Macklem <rmacklem@uoguelph.ca> wrote: > > > ... one of the fundamental principals for NFSv2, 3 was a stateless > > server ... > > Only as long as UDP transport was used. Any NFS implementation that > used TCP for transport had thereby abandoned the stateless server > principle, since a TCP connection itself requires that state be > maintained on both ends. Not filesystem cache coherency state, only socket state. And even NFS UDP mounts maintain their own set of "socket" state to manage retries and retransmits for UDP RPCs. The filesystem is equally incoherent for both UDP and TCP NFSv[23] mounts. TCP did not change any of that. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201101050757.08116.jhb>