Re: "Re: [PATCH RFC Version 1 0/6] Request for Comment: NFS4.1 Session Trunking"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux