public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom Haynes <thomas.haynes@primarydata.com>
To: Christoph Hellwig <hch@lst.de>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org,
	Jeff Layton <jlayton@primarydata.com>,
	xfs@oss.sgi.com
Subject: Re: [PATCH 10/18] nfsd: implement pNFS layout recalls
Date: Tue, 6 Jan 2015 09:59:44 -0800	[thread overview]
Message-ID: <20150106175943.GA14225@kitty.kitty> (raw)
In-Reply-To: <20150106174214.GB16200@lst.de>

On Tue, Jan 06, 2015 at 06:42:14PM +0100, Christoph Hellwig wrote:
> > 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
> 

I don't know if I would say zero interest or normal apathy on the
NFSv4 WG list to replying outside of the IETF meeting venue.

I'd certainly like to see it go forward.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2015-01-06 17:59 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 16:28 a simple and scalable pNFS block layout server Christoph Hellwig
2015-01-06 16:28 ` [PATCH 01/18] nfs: add LAYOUT_TYPE_MAX enum value Christoph Hellwig
2015-01-06 16:28 ` [PATCH 02/18] fs: add FL_LAYOUT lease type Christoph Hellwig
2015-01-06 18:46   ` Jeff Layton
2015-01-07 10:30     ` Christoph Hellwig
2015-01-06 16:28 ` [PATCH 03/18] nfsd: factor out a helper to decode nfstime4 values Christoph Hellwig
2015-01-09 23:02   ` Tom Haynes
2015-01-11 11:42     ` Christoph Hellwig
2015-01-11 23:53       ` Tom Haynes
2015-01-06 16:28 ` [PATCH 04/18] nfsd: move nfsd_fh_match to nfsfh.h Christoph Hellwig
2015-01-06 16:28 ` [PATCH 05/18] nfsd: add fh_fsid_match helper Christoph Hellwig
2015-01-06 16:28 ` [PATCH 06/18] nfsd: make lookup/alloc/unhash_stid available outside nfs4state.c Christoph Hellwig
2015-01-06 16:28 ` [PATCH 07/18] nfsd: make find/get/put file " Christoph Hellwig
2015-01-06 16:28 ` [PATCH 08/18] nfsd: make find_any_file " Christoph Hellwig
2015-01-06 16:28 ` [PATCH 09/18] nfsd: implement pNFS operations Christoph Hellwig
2015-01-09  0:48   ` Jeff Layton
2015-01-09 10:05     ` Christoph Hellwig
2015-01-09 16:51       ` Jeff Layton
2015-01-09 17:16         ` Christoph Hellwig
2015-01-09 17:28           ` Jeff Layton
2015-01-09 17:33             ` Jeff Layton
2015-01-09 17:43               ` Trond Myklebust
2015-01-12 17:54   ` Tom Haynes
2015-01-06 16:28 ` [PATCH 10/18] nfsd: implement pNFS layout recalls Christoph Hellwig
2015-01-06 17:25   ` J. Bruce Fields
2015-01-06 17:42     ` Christoph Hellwig
2015-01-06 17:59       ` Tom Haynes [this message]
2015-01-06 16:28 ` [PATCH 11/18] nfsd: update documentation for pNFS support Christoph Hellwig
2015-01-06 16:28 ` [PATCH 12/18] nfsd: add trace events Christoph Hellwig
2015-01-06 16:28 ` [PATCH 13/18] exportfs: add methods for block layout exports Christoph Hellwig
2015-01-06 16:28 ` [PATCH 14/18] nfsd: pNFS block layout driver Christoph Hellwig
2015-01-06 17:16   ` J. Bruce Fields
2015-01-06 17:39     ` Christoph Hellwig
2015-01-06 19:39       ` J. Bruce Fields
2015-01-06 19:42         ` Jeff Layton
2015-01-07 10:28           ` Christoph Hellwig
2015-01-08 20:41             ` Jeff Layton
2015-01-08 20:54               ` J. Bruce Fields
2015-01-12  4:56   ` Tom Haynes
2015-01-12 12:43     ` Christoph Hellwig
2015-01-12  6:14   ` Tom Haynes
2015-01-12 12:46     ` Christoph Hellwig
2015-01-06 16:28 ` [PATCH 15/18] xfs: pass a 64-bit count argument to xfs_iomap_write_unwritten Christoph Hellwig
2015-01-06 16:28 ` [PATCH 16/18] xfs: do not allocate blocks when converting unwritten extents Christoph Hellwig
2015-01-06 23:21   ` Dave Chinner
2015-01-06 16:28 ` [PATCH 17/18] xfs: implement pnfs export operations Christoph Hellwig
2015-01-07  0:24   ` Dave Chinner
2015-01-07 10:40     ` Christoph Hellwig
2015-01-07 21:11       ` Dave Chinner
2015-01-08 12:43         ` Christoph Hellwig
2015-01-08 21:04           ` Dave Chinner
2015-01-09 11:41             ` Christoph Hellwig
2015-01-12  3:04               ` Dave Chinner
2015-01-14 10:08                 ` Christoph Hellwig
2015-01-06 16:28 ` [PATCH 18/18] xfs: recall pNFS layouts on conflicting access Christoph Hellwig
2015-01-06 23:18   ` Dave Chinner
2015-01-07 10:31     ` Christoph Hellwig
2015-01-06 17:32 ` a simple and scalable pNFS block layout server J. Bruce Fields
2015-01-06 17:56   ` Christoph Hellwig
2015-01-06 18:37     ` Jeff Layton
2015-01-06 18:39       ` Weston Andros Adamson
2015-01-06 19:17     ` 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=20150106175943.GA14225@kitty.kitty \
    --to=thomas.haynes@primarydata.com \
    --cc=bfields@fieldses.org \
    --cc=hch@lst.de \
    --cc=jlayton@primarydata.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=xfs@oss.sgi.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