From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Tom Talpey <tom@talpey.com>, Jeff Layton <jlayton@redhat.com>,
trond.myklebust@primarydata.com, schumaker.anna@gmail.com,
linux-nfs@vger.kernel.org, Chuck Lever <chuck.lever@oracle.com>,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH 1/4] sunrpc: flag transports as using IETF approved congestion control protocols
Date: Thu, 23 Feb 2017 13:26:09 -0700 [thread overview]
Message-ID: <20170223202609.GC26301@obsidianresearch.com> (raw)
In-Reply-To: <20170223201109.GC11882@fieldses.org>
On Thu, Feb 23, 2017 at 03:11:09PM -0500, J. Bruce Fields wrote:
> (And if we really shouldn't be doing NFSv4 over some RDMA transports--is
> it worth supporting them at all, if the only support we can get is
> NFSv3-only?)
This seems like a strange comment - NFSv4 should be supported on all
RDMA transports, surely?
Largely RDMA lives in its own congestion management world. If a site
is running RDMA they have done something to mitigate interactions with
TCP style congestion control on the same wire.
Jason
next prev parent reply other threads:[~2017-02-23 20:27 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 17:03 [PATCH 0/4] nfs/nfsd/sunrpc: enforce requirement for congestion control protocols in NFSv4 Jeff Layton
2017-02-23 17:03 ` [PATCH 1/4] sunrpc: flag transports as using IETF approved congestion control protocols Jeff Layton
2017-02-23 19:42 ` Tom Talpey
2017-02-23 20:00 ` Jeff Layton
2017-02-23 20:06 ` Tom Talpey
2017-02-23 20:11 ` J. Bruce Fields
2017-02-23 20:26 ` Jason Gunthorpe [this message]
2017-02-23 20:33 ` Tom Talpey
2017-02-23 20:55 ` Jason Gunthorpe
2017-02-24 15:08 ` Tom Talpey
2017-02-24 17:17 ` Jeff Layton
2017-02-24 18:03 ` Jason Gunthorpe
2017-02-23 20:32 ` Jeff Layton
2017-02-23 20:17 ` Chuck Lever
2017-02-23 20:15 ` Chuck Lever
2017-02-23 17:03 ` [PATCH 2/4] sunrpc: turn bitfield flags in svc_version into bools Jeff Layton
2017-02-23 17:03 ` [PATCH 3/4] nfs/nfsd/sunrpc: enforce congestion control protocol requirement for NFSv4 Jeff Layton
2017-02-23 17:03 ` [PATCH 4/4] sunrpc: don't register UDP port with rpcbind when version needs congestion control Jeff Layton
2017-02-23 17:17 ` [PATCH 0/4] nfs/nfsd/sunrpc: enforce requirement for congestion control protocols in NFSv4 Jeff Layton
2017-02-24 18:25 ` [PATCH v2 0/4] nfs/nfsd/sunrpc: enforce NFSv4 transport requirements Jeff Layton
2017-02-24 18:25 ` [PATCH v2 1/4] sunrpc: turn bitfield flags in svc_version into bools Jeff Layton
2017-02-24 18:25 ` [PATCH v2 2/4] sunrpc: flag transports as having both reliable and ordered delivery, and congestion control Jeff Layton
2017-02-24 18:25 ` [PATCH v2 3/4] nfs/nfsd/sunrpc: enforce transport requirements for NFSv4 Jeff Layton
2017-02-24 18:25 ` [PATCH v2 4/4] sunrpc: don't register UDP port with rpcbind when version needs congestion control Jeff Layton
2017-02-24 18:38 ` [PATCH v2 0/4] nfs/nfsd/sunrpc: enforce NFSv4 transport requirements Chuck Lever
2017-02-24 18:53 ` Jeff Layton
2017-02-24 21:23 ` J. Bruce Fields
2017-02-24 18:53 ` Tom Talpey
2017-02-24 21:22 ` J. Bruce Fields
2017-02-24 21:25 ` J. Bruce Fields
2017-02-24 21:34 ` Jeff Layton
2017-02-24 21:44 ` J. Bruce Fields
2017-02-27 11:59 ` Jeff Layton
2017-02-27 12:08 ` Tom Talpey
2017-02-27 12:55 ` Jeff Layton
2017-02-27 14:20 ` 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=20170223202609.GC26301@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=schumaker.anna@gmail.com \
--cc=tom@talpey.com \
--cc=trond.myklebust@primarydata.com \
/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;
as well as URLs for NNTP newsgroup(s).