From: Greg Banks <gnb-cP1dWloDopni96+mSzHFpQC/G2K4zDHf@public.gmane.org>
To: Neil Brown <neilb@suse.de>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [grumble] connected UDP sockets [grumble] Solaris [grumble]
Date: Thu, 23 Oct 2008 15:47:06 +1100 [thread overview]
Message-ID: <490001CA.8010801@melbourne.sgi.com> (raw)
In-Reply-To: <18687.63003.966163.267177-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
Neil Brown wrote:
>
> Much as it pains me to say this, maybe we just need to treat UDP as
> legacy for all protocols (PORTMAP, MOUNT, NLM, NSM), not just NFS.
> None of these problems occur with TCP. TCP does have a slightly
> higher overhead for simple transactions, but it is a cost that is
> unlikely to be noticeable in reality.
>
>
> Thoughts?
>
>
I see only two reasons to keep any UDP support at all in either client
or server.
a) legacy compatibility, for toy/broken/antique clients/servers/firewalls
b) on the server, supporting broadcast RPC to/through the portmapper
--
Greg Banks, P.Engineer, SGI Australian Software Group.
Be like the squirrel.
I don't speak for SGI.
next prev parent reply other threads:[~2008-10-23 4:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 3:57 [grumble] connected UDP sockets [grumble] Solaris [grumble] Neil Brown
[not found] ` <18687.63003.966163.267177-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-10-23 4:47 ` Greg Banks [this message]
2008-10-23 16:05 ` Chuck Lever
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=490001CA.8010801@melbourne.sgi.com \
--to=gnb-cp1dwlodopni96+mszhfpqc/g2k4zdhf@public.gmane.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
/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