All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Banks <gnb@melbourne.sgi.com>
To: Steve Dickson <SteveD@RedHat.com>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
	Linux NFS Mailing List <nfs@lists.sourceforge.net>
Subject: Re: [PATCH] SGI 904217 (2/2): allow enabling TCP without recompile
Date: Tue, 16 Dec 2003 13:16:19 +1100	[thread overview]
Message-ID: <3FDE6AF3.552F659@melbourne.sgi.com> (raw)
In-Reply-To: 3FDE6748.7090404@RedHat.com

Steve Dickson wrote:
> 
> Greg Banks wrote:
> 
> >These two patches Linux systems to be shipped with CONFIG_NFSD_TCP=y
> >but TCP support disabled at runtime until the sysadmin edits the
> >/etc/sysconfig/nfs file and restarts NFS.  The idea is that TCP
> >support is still disabled by default, but can be enabled with less
> >pain than currently is the case (we have customers who want to try
> >it).
> >
> >
> Why disable it? Since UPD is still mountd's default transport..

This depends on client options outside the scope of the patch, e.g. how
the client's fstab or autofs is configured.  Some clients will try TCP
first and then fall back to UDP when it fails; if the TCP mount suddenly
starts working, that's a visible change.

> >The second patch is for nfs-utils and adds a -t option to nfsd which
> >uses the new nfsctl (added in the first patch) to enable specific
> >transports, and the infrastructure to allow the sysadmin to specify
> >it easily.  Default is to enable UDP only for compatibility.
> >
> >
> This seems a bit messy.... Why not just turn on TCP and have
> nfsd listen on both types of transports?

I don't want to perturb the way in which bits flow across the wire
without the sysadmin's explicit intervention.  This is purely a
support issue, not a technical one.

Greg.
-- 
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2003-12-16  2:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-15  8:14 [PATCH] SGI 904217 (2/2): allow enabling TCP without recompile Greg Banks
2003-12-16  2:00 ` Steve Dickson
2003-12-16  2:16   ` Greg Banks [this message]

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=3FDE6AF3.552F659@melbourne.sgi.com \
    --to=gnb@melbourne.sgi.com \
    --cc=SteveD@RedHat.com \
    --cc=neilb@cse.unsw.edu.au \
    --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.