From: Tom Haynes <tdh@excfb.com>
To: peter.staubach@emc.com
Cc: Zoltan.Menyhart@bull.net, chuck.lever@oracle.com,
linux-nfs@vger.kernel.org
Subject: Re: NFS v4 client blocks when using UDP protocol
Date: Tue, 29 Mar 2011 19:12:32 -0500 [thread overview]
Message-ID: <20110330001232.GB19700@adept.internal.excfb.com> (raw)
In-Reply-To: <5E6794FC7B8FCA41A704019BE3C70E8B069D40C4@MX31A.corp.emc.com>
On Tue, Mar 29, 2011 at 11:50:36AM -0400, peter.staubach@emc.com wrote:
> It does talk about NFS over UDP, interestingly, but the text on page 25, indicates that the transport of choice MUST be one of the IETF-approved congestion control transport protocols, of which, UDP is not one.
>
> Perhaps some clean up of RFC3530bis and RFC5661 could include removal of the UDP mentions.
The text in 3530bis could be made to match that in 5661:
It is permissible for a connectionless transport to be used under
NFSv4.1; however, reliable and in-order delivery of data combined
with congestion control by the connectionless transport is REQUIRED.
As a consequence, UDP by itself MUST NOT be used as an NFSv4.1
transport. NFSv4.1 assumes that a client transport address and
server transport address used to send data over a transport together
constitute a connection, even if the underlying transport eschews the
concept of a connection.
But as we can see 5661 is very strong.
>
> ps
>
>
> -----Original Message-----
> From: linux-nfs-owner@vger.kernel.org [mailto:linux-nfs-owner@vger.kernel.org] On Behalf Of Menyhart Zoltan
> Sent: Tuesday, March 29, 2011 11:26 AM
> To: Chuck Lever
> Cc: linux-nfs@vger.kernel.org
> Subject: Re: NFS v4 client blocks when using UDP protocol
>
> Chuck Lever wrote:
> > Zoltan-
> >
> > As far as I know, NFSv4 is not supported on UDP transports.
> >Some of it may work, but no warrantee, either expressed or implied, is given. :-)
>
> Do you mean the Linux implementation?
> Because the RFC 3530 speaks about how to do NFS v4 over UDP and UDP6.
>
> Thank you,
>
> Zoltan
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Tom Haynes
ex-cfb
next prev parent reply other threads:[~2011-03-30 0:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EB0F26AF-C0DB-4861-ABB5-72E39CB38090@bull.net>
2011-03-29 14:32 ` NFS v4 client blocks when using UDP protocol Menyhart Zoltan
2011-03-29 15:06 ` Chuck Lever
2011-03-29 15:26 ` Menyhart Zoltan
2011-03-29 15:46 ` Chuck Lever
2011-03-29 15:50 ` peter.staubach
2011-03-30 0:12 ` Tom Haynes [this message]
2011-03-30 9:00 ` Trond Myklebust
2011-11-10 8:11 fanchaoting
2011-11-10 14:50 ` Myklebust, Trond
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110330001232.GB19700@adept.internal.excfb.com \
--to=tdh@excfb.com \
--cc=Zoltan.Menyhart@bull.net \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=peter.staubach@emc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).