From: "Matt W. Benjamin" <matt@cohortfs.com>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [RFC PATCH v3 13/13] pnfs/NFSv4.1: Add multipath capabilities to pNFS flexfiles servers over NFSv3
Date: Mon, 1 Feb 2016 12:31:22 -0500 (EST) [thread overview]
Message-ID: <1329865363.28.1454347882962.JavaMail.root@thunderbeast.private.linuxbox.com> (raw)
In-Reply-To: <1454347277-10997-14-git-send-email-trond.myklebust@primarydata.com>
Hi Trond,
----- "Trond Myklebust" <trond.myklebust@primarydata.com> wrote:
> This adds multipathing to pNFS over NFSv3 as described in the
> flexfiles
> draft spec.
> Ideally, we'd like to do the same for pNFS files, but the NFSv4.1
> protocol
> requires a call to EXCHANGE_ID in order to test that the connection
> can do
> session trunking.
What is the barrier to sending this to data servers as needed?
>
> Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
> ---
> fs/nfs/pnfs_nfs.c | 16 +++++++++++++---
> 1 file changed, 13 insertions(+), 3 deletions(-)
>
Matt
--
Matt Benjamin
CohortFS, LLC.
315 West Huron Street, Suite 140A
Ann Arbor, Michigan 48103
http://cohortfs.com
tel. 734-761-4689
fax. 734-769-8938
cel. 734-216-5309
next prev parent reply other threads:[~2016-02-01 17:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 17:21 [RFC PATCH v3 00/13] Basic multipathing support and demonstrator Trond Myklebust
2016-02-01 17:21 ` [RFC PATCH v3 01/13] SUNRPC: Remove unused function rpc_task_reset_client Trond Myklebust
2016-02-01 17:21 ` [RFC PATCH v3 02/13] SUNRPC: Reorder rpc_task to put waitqueue related info in same cachelines Trond Myklebust
2016-02-01 17:21 ` [RFC PATCH v3 03/13] SUNRPC: Uninline xprt_get(); It isn't performance critical Trond Myklebust
2016-02-01 17:21 ` [RFC PATCH v3 04/13] SUNRPC: Make freeing of struct xprt rcu-safe Trond Myklebust
2016-02-01 17:21 ` [RFC PATCH v3 05/13] SUNRPC: Add a structure to track multiple transports Trond Myklebust
2016-02-01 17:21 ` [RFC PATCH v3 06/13] SUNRPC: Make rpc_clnt store the multipath iterators Trond Myklebust
2016-02-01 17:21 ` [RFC PATCH v3 07/13] SUNRPC: Use the multipath iterator to assign a transport to each task Trond Myklebust
2016-02-01 17:21 ` [RFC PATCH v3 08/13] SUNRPC: Allow caller to specify the transport to use Trond Myklebust
2016-02-01 17:21 ` [RFC PATCH v3 09/13] SUNRPC: Add a helper to apply a function to all the rpc_clnt's transports Trond Myklebust
2016-02-01 17:21 ` [RFC PATCH v3 10/13] SUNRPC: Make NFS swap work with multipath Trond Myklebust
2016-02-01 17:21 ` [RFC PATCH v3 11/13] NFSv4.1: nfs4_proc_bind_conn_to_session must iterate over all connections Trond Myklebust
2016-02-01 17:21 ` [RFC PATCH v3 12/13] SUNRPC: Allow addition of new transports to a struct rpc_clnt Trond Myklebust
2016-02-01 17:21 ` [RFC PATCH v3 13/13] pnfs/NFSv4.1: Add multipath capabilities to pNFS flexfiles servers over NFSv3 Trond Myklebust
2016-02-01 17:31 ` Matt W. Benjamin [this message]
2016-02-01 20:48 ` [RFC PATCH v3 00/13] Basic multipathing support and demonstrator J. Bruce Fields
2016-02-01 21:12 ` Trond Myklebust
2016-02-01 21:54 ` Tom Talpey
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=1329865363.28.1454347882962.JavaMail.root@thunderbeast.private.linuxbox.com \
--to=matt@cohortfs.com \
--cc=linux-nfs@vger.kernel.org \
--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).