| To: | "J. Bruce Fields" <bfields@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 10/18] nfsd: implement pNFS layout recalls |
| From: | Christoph Hellwig <hch@xxxxxx> |
| Date: | Tue, 6 Jan 2015 18:42:14 +0100 |
| Cc: | Christoph Hellwig <hch@xxxxxx>, Jeff Layton <jlayton@xxxxxxxxxxxxxxx>, linux-nfs@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20150106172508.GE12067@xxxxxxxxxxxx> |
| References: | <1420561721-9150-1-git-send-email-hch@xxxxxx> <1420561721-9150-11-git-send-email-hch@xxxxxx> <20150106172508.GE12067@xxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.17 (2007-11-01) |
> This bothers me a little: cl_addr is just the address that the > exchange_id came from. In theory there's no one-to-one relationship > between NFSv4 clients and IP addresses. Is it likely the iscsi traffic > could use a different interface than the MDS traffic? > > If this is the best we can do, then maybe this should at least be > documented. The pNFS block fencing protocol bothers me a lot, it seems like very little thought went into that part of the standard. I proposed a new SCSI layout type that fixes those issues on the NFSv4 WG list, but there's been zero interest in it: http://www.ietf.org/mail-archive/web/nfsv4/current/msg13469.html |
| Previous by Date: | Re: [PATCH 14/18] nfsd: pNFS block layout driver, Christoph Hellwig |
|---|---|
| Next by Date: | Re: a simple and scalable pNFS block layout server, Christoph Hellwig |
| Previous by Thread: | Re: [PATCH 10/18] nfsd: implement pNFS layout recalls, J. Bruce Fields |
| Next by Thread: | Re: [PATCH 10/18] nfsd: implement pNFS layout recalls, Tom Haynes |
| Indexes: | [Date] [Thread] [Top] [All Lists] |