Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: "Adamson, Andy" <William.Adamson@netapp.com>,
	Trond Myklebust <trond.myklebust@primarydata.com>,
	Martin Houry <martinhoury@gmail.com>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: "Re: [PATCH RFC Version 1 0/6] Request for Comment: NFS4.1 Session Trunking"
Date: Fri, 19 Feb 2016 10:01:35 -0500	[thread overview]
Message-ID: <20160219150135.GD17042@fieldses.org> (raw)
In-Reply-To: <336DFCFA-5655-4CB1-82F2-9E3B17030094@oracle.com>

On Thu, Feb 18, 2016 at 04:29:46PM -0500, Chuck Lever wrote:
> True; there's a reason I never got to implementing
> fs_locations_info on the Linux server for FedFS. There
> are sticky problems around the mountd upcall that is
> used to communicate this information to the kernel,
> for example.
> 
> However, I don't agree that this is a good reason to
> go with multiple hostnames on the mount command line.
> I like Andy's plan to keep this CLI change out of the
> long term upstream code, but continue to use it for
> testing.

Even if we get an fs_locations_info-based solution to the point where
it's the best default, don't you think we'll still want some kind of
manual override on the client?

The decision here has to do with the path between client and server,
and the server may not always be in the best position to make that
decision.

--b.

  reply	other threads:[~2016-02-19 15:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17 10:31 "Re: [PATCH RFC Version 1 0/6] Request for Comment: NFS4.1 Session Trunking" Martin Houry
2016-02-17 14:50 ` Adamson, Andy
2016-02-17 16:34   ` J. Bruce Fields
2016-02-17 17:49     ` Adamson, Andy
2016-02-17 18:44       ` J. Bruce Fields
2016-02-17 19:57         ` Adamson, Andy
2016-02-17 19:06   ` Chuck Lever
2016-02-17 20:59     ` J. Bruce Fields
2016-02-17 22:35       ` Adamson, Andy
2016-02-17 22:52         ` Chuck Lever
2016-02-17 23:55           ` Trond Myklebust
2016-02-18 14:14             ` J. Bruce Fields
2016-02-18 14:38               ` Martin Houry
2016-02-18 18:32               ` Trond Myklebust
2016-02-18 19:41                 ` Adamson, Andy
2016-02-18 20:39                   ` J. Bruce Fields
2016-02-18 21:29                     ` Chuck Lever
2016-02-19 15:01                       ` J. Bruce Fields [this message]
2016-02-19 16:29                         ` Chuck Lever
2016-02-18 14:05           ` J. Bruce Fields
2016-02-18 11:28   ` Martin Houry

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=20160219150135.GD17042@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=William.Adamson@netapp.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=martinhoury@gmail.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