From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Thomas Haynes <thomas@netapp.com>,
DENIEL Philippe <philippe.deniel@cea.fr>,
linux-nfs@vger.kernel.org
Subject: Re: Side effects of having NFSv4 mounted over udp
Date: Mon, 13 Dec 2010 14:47:35 -0500 [thread overview]
Message-ID: <1292269655.8795.7.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <20101213191634.GB2230@fieldses.org>
On Mon, 2010-12-13 at 14:16 -0500, J. Bruce Fields wrote:
> On Mon, Dec 13, 2010 at 01:04:28PM -0600, Thomas Haynes wrote:
> >
> > On Dec 13, 2010, at 1:46 AM, DENIEL Philippe wrote:
> >
> > > Hi,
> > >
> > > I know NFSv4 is definitely a connection oriented protocol, but noting prevent from using "mount -t nfs4 -o proto=udp <...>". Using TCP instead of UDP could be of great interest, especially in a HPC context where thousands of clients will operate at the same time. If a nfs mount point is made over udp, what would be the side effects ? I tried to run the connectathon on such a udp based mount point and I could find no errors. Is NFSv4/UDP a suitable solution ? Or does it make no sense to use udp ?
> >
> >
> > You might find that some implementations have UDP disabled and it might then make
> > it hard to triage what is going on.
> >
> > I believe both NetApp's OnTap and Oracle's Solaris have it turned off.
>
> The Linux server allows it, but I've been considering that a
> (low-priority) bug, so it wouldn't be safe to assume it will continue
> working.
>
> That aside, if you have a perfect network, NFSv4.0 at least will
> probably work. (Not 4.1 since backchannel setup will fail?)
>
> Are you really sure that you can't make tcp scale to thousands of
> clients?
Maybe SCTP would be the way to go then? We've often talked about it over
the years, but nobody has yet (to my knowledge) written an ONC RPC
transport for it.
Cheers
Trond
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
next prev parent reply other threads:[~2010-12-13 19:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 7:46 Side effects of having NFSv4 mounted over udp DENIEL Philippe
2010-12-13 19:04 ` Thomas Haynes
2010-12-13 19:16 ` J. Bruce Fields
2010-12-13 19:47 ` Trond Myklebust [this message]
2010-12-14 7:35 ` DENIEL Philippe
2010-12-14 19:15 ` J. Bruce Fields
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=1292269655.8795.7.camel@heimdal.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=philippe.deniel@cea.fr \
--cc=thomas@netapp.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).