Linux NFS development
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Greg Banks <gnb-cP1dWloDopni96+mSzHFpQC/G2K4zDHf@public.gmane.org>
Cc: Chuck Lever <chuck.lever@oracle.com>,
	Trond Myklebust <trond.myklebust@fys.uio.no>,
	bfields@citi.umich.edu, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 4/5] NFSD: Remove NFSD_TCP kernel build option
Date: Tue, 5 Feb 2008 17:05:56 +1100	[thread overview]
Message-ID: <18343.64708.19074.639419@notabene.brown> (raw)
In-Reply-To: message from Greg Banks on Tuesday February 5

On Tuesday February 5, gnb-cP1dWloDopni96+mSzHFpQC/G2K4zDHf@public.gmane.org wrote:
> >
> > What might make sense is to remove NFSD_TCP, but add NFSD_UDP,
> > defaulting to Y.
> >
> > Then in a year or two we can change the default to N.
> >
> Fine by me.

I, on the other hand, think we should leave support for UDP and TCP in
the kernel indefinitely and rely on the 'rpc.nfsd' tool to choose
what to listen to.


NeilBrown

  reply	other threads:[~2008-02-05  6:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05  0:04 [PATCH 4/5] NFSD: Remove NFSD_TCP kernel build option Chuck Lever
     [not found] ` <20080205000442.18602.29035.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-02-05  0:19   ` Greg Banks
     [not found]     ` <47A7AB89.7020709-cP1dWloDopni96+mSzHFpQC/G2K4zDHf@public.gmane.org>
2008-02-05  0:19       ` Trond Myklebust
     [not found]         ` <1202170754.28484.57.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-02-05  0:29           ` Greg Banks
     [not found]             ` <47A7AE03.10401-cP1dWloDopni96+mSzHFpQC/G2K4zDHf@public.gmane.org>
2008-02-05  1:55               ` Chuck Lever
2008-02-05  5:49                 ` Greg Banks
2008-02-05  6:05                   ` Neil Brown [this message]
     [not found]                   ` <47A7F8F3.3020907-cP1dWloDopni96+mSzHFpQC/G2K4zDHf@public.gmane.org>
2008-02-05 15:50                     ` Frank van Maarseveen
2008-02-05 17:50                       ` Trond Myklebust
     [not found]                         ` <1202233839.8452.31.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-02-05 18:08                           ` Frank van Maarseveen
2008-02-05 23:05                       ` Greg Banks
     [not found]                         ` <47A8EBC3.7050900-cP1dWloDopni96+mSzHFpQC/G2K4zDHf@public.gmane.org>
2008-02-05 23:08                           ` 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=18343.64708.19074.639419@notabene.brown \
    --to=neilb@suse.de \
    --cc=bfields@citi.umich.edu \
    --cc=chuck.lever@oracle.com \
    --cc=gnb-cP1dWloDopni96+mSzHFpQC/G2K4zDHf@public.gmane.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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