All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Kegel <dkegel@ixiacom.com>
To: nfs@lists.sourceforge.net
Subject: Meaning of 'udp' mount option
Date: Mon, 30 Jun 2003 12:35:58 -0700	[thread overview]
Message-ID: <3F00911E.5020001@ixiacom.com> (raw)

Question 1: what does the 'udp' mount option really mean?
It appears to mean 'Use udp mostly, but use TCP when calling pmap_getmaps()'.
Question 2: is this a bug or a feature?
Question 3: if it's a feature, should we add a new mount option to
mean 'really, dude, use udp for everything'?

The long story:

Imagine, if you will, an NFS server running on an operating system
that will shut down all further TCP connects on a given port if that
port ever encounters more than five simultaneous connects.
(That's a rather perverse limitation, but unfortunately, it seems to
be widespread.)

Imagine further that you have 500 NFS clients that want to connect
simultaneously to that server.  "Ah, simple, I'll just use UDP, and
avoid the issue!", you say.

Unfortunately, it appears that even when you specify UDP as a
mount option, util-linux-2.11[nz]'s mount appears
to always connect to the server's portmapper using TCP.  The
culprit is glibc's pmap_getmaps, which always uses tcp.

I threw together a version of rpcinfo.c that uses udp to do
the same thing as pmap_getmaps, and it works.

The next step is for me to patch nfsmount.c's get_mountport()
to only use the standard pmap_getmaps() if mounting via TCP,
and to use my pmap_getmaps_via_udp() if mounting via UDP.

If that works, then presumably it'd be nice to fold something
like this in to the main tree.  But making the 'udp' mount
option really mean 'udp, goddammit' might be too much of a
change in semantics; perhaps there should be a new mount option
always_udp?

- Dan



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2003-06-30 19:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-30 19:35 Dan Kegel [this message]
2003-06-30 22:24 ` [PATCH] Make 'udp' mount option really mean it (was: Meaning of 'udp' mount option) Dan Kegel
2003-06-30 22:29   ` [PATCH] Make 'udp' mount option really mean it Dan Kegel

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=3F00911E.5020001@ixiacom.com \
    --to=dkegel@ixiacom.com \
    --cc=nfs@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.