From: "Frank Filz" <ffilzlnx@mindspring.com>
To: <dang@redhat.com>, "'Olga Kornievskaia'" <aglo@umich.edu>,
"'linux-nfs'" <linux-nfs@vger.kernel.org>
Subject: RE: support for UDP
Date: Fri, 13 Sep 2019 09:16:23 -0700 [thread overview]
Message-ID: <09ff01d56a4e$96857660$c3906320$@mindspring.com> (raw)
In-Reply-To: <080bf93a-0e66-bb56-a54f-5496c688bb70@redhat.com>
> On 9/13/19 11:14 AM, Olga Kornievskaia wrote:
> > Hi folks,
> >
> > I'd like to gauge what people think. Do you think we'd ever do a bold
> > thing like drop the UDP support in the upstream kernel (obviously with
> > a plan to fade it out with a config option that we did with the des
> > support)...
> >
>
> Yes, please.
Yea, it would certainly be nice to not have to worry about UDP connections. They don't work for NFS in high speed high bandwidth workloads due to the issues with fragment reassembly. Their use for NFS v3 sideband protocols doesn't really buy much.
Of course we'll still have to support UDP for 10 more years...
Frank
next prev parent reply other threads:[~2019-09-14 3:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 15:14 support for UDP Olga Kornievskaia
2019-09-13 15:37 ` Daniel Gryniewicz
2019-09-13 16:16 ` Frank Filz [this message]
2019-09-19 13:40 ` Steve Dickson
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='09ff01d56a4e$96857660$c3906320$@mindspring.com' \
--to=ffilzlnx@mindspring.com \
--cc=aglo@umich.edu \
--cc=dang@redhat.com \
--cc=linux-nfs@vger.kernel.org \
/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