From: Mike Eisler (mike@eisler.com)
Date: 11/25/02-05:34:39 PM Z
Message-ID: <3DE2B38F.F6B3BC0A@eisler.com>
Date: Mon, 25 Nov 2002 15:34:39 -0800
From: Mike Eisler <mike@eisler.com>
Subject: Re: heads up - NetApp, NFSv4, and UDP
No, he's responding to the claim that it comes for free because
same rpc is used for { udp, tcp } X { v2, v3 }. Dave's point is it
isn't free because NFSv4 over TCP establishes a new convenant that
did not exist with NFSv[23] over TCP.
NFSv[23] servers can and do cheerfully drop requests without breaking the
the TCP connection.
-mre
Trond Myklebust wrote:
>
> >>>>> " " == Dave Noveck <Noveck> writes:
>
> > Sometimes what comes for free has hidden costs. In particular,
> > if you use the same rpc that comes with v3, you are going to be
> > re-issuing requests on TCP connections, under cirsumstances in
> > which the v4 spec (section 3.1.1) says you MUST NOT do so:
>
> I hope you are not saying that it is impossible to be sharing the same
> RPC engine between v2/v3 and v4?
>
> Section 3.1.1 explicitly states that the client is allowed to break
> the transport connection and then resend the request (even after it
> has determined that the server is still alive). IIRC that was added
> specifically in order to allow RPC engine reuse with v2 and v3.
>
> Cheers,
> Trond
This archive was generated by hypermail 2.1.2 : 03/04/05-01:50:30 AM Z CST