All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Fred Isaman <iisaman@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 00/12] pnfs: LAYOUTGET/DEVINFO submission v5
Date: Thu, 21 Oct 2010 17:12:08 -0400	[thread overview]
Message-ID: <1287695528.16982.4.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <1287548284-28374-1-git-send-email-iisaman@netapp.com>

On Wed, 2010-10-20 at 00:17 -0400, Fred Isaman wrote:
> This is try 5 of the first wave of the linux pnfs client submission.
> The only change (besides rebase on top of Trond's most recent
> nfs-for-2.6.37 branch) between this series and the previous is that
> owner/sign-off issues have been addressed, which allows us to
> remove the RFC label of the previous series.
> 
> For those interested, the patches themselves can also be found at
> git://linux-nfs.org/~iisaman/linux-pnfs.git,
> branch devinfo-submit-rc7-trond
> 
> 
> This is the start of code implementing pnfs, based on RFC 5661.  Since
> sending the whole thing at once would be overwhelming, we are trying
> to break it into bite sized waves.  This first wave implements the
> mount/umount infrastructure, as well as sending the LAYOUTGET and
> GETDEVTICEINFO calls on io (but not actually using the information for
> io).  Note that two major simplifications to the protocol will be made 
> throughout the initial submission process:  only the file layout
> driver is considered, and only whole file layouts are requested.
> 
> 
> These patches apply against Trond's nfs-for-2.6.37 branch.
> 
> patches 01-08 implement the mount/umount hooks
> patches 09-12 implement LAYOUTGET and GETDEVICEINFO

OK. I merged these patches for testing in linux-next last night. If all
goes well, I'll send them to Linus in this merge window.

Trond

      parent reply	other threads:[~2010-10-21 21:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-20  4:17 [PATCH 00/12] pnfs: LAYOUTGET/DEVINFO submission v5 Fred Isaman
2010-10-20  4:17 ` [PATCH 01/12] NFSD: remove duplicate NFS4_STATEID_SIZE Fred Isaman
2010-10-20  4:17 ` [PATCH 02/12] SUNRPC: define xdr_decode_opaque_fixed Fred Isaman
2010-10-20  4:17 ` [PATCH 03/12] NFSv4.1: pnfsd, pnfs: protocol level pnfs constants Fred Isaman
2010-10-20  4:17 ` [PATCH 04/12] NFS: change stateid to be a union Fred Isaman
2010-10-20  4:17 ` [PATCH 05/12] NFS: ask for layouttypes during v4 fsinfo call Fred Isaman
2010-10-20  4:17 ` [PATCH 06/12] NFS: set layout driver Fred Isaman
2010-10-20  4:17 ` [PATCH 07/12] NFSv4.1: pnfs: full mount/umount infrastructure Fred Isaman
2010-10-20  4:18 ` [PATCH 08/12] NFSv4.1: pnfs: filelayout: introduce minimal file layout driver Fred Isaman
2010-10-20  4:18 ` [PATCH 09/12] NFS: create and destroy inode's layout cache Fred Isaman
2010-10-20  4:18 ` [PATCH 10/12] NFS: client needs to maintain list of inodes with active layouts Fred Isaman
2010-10-20  4:18 ` [PATCH 11/12] NFSv4.1: pnfs: add LAYOUTGET and GETDEVICEINFO infrastructure Fred Isaman
2010-10-20  4:18 ` [PATCH 12/12] NFSv4.1: pnfs: filelayout: add driver's " Fred Isaman
2010-10-21 21:12 ` Trond Myklebust [this message]

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=1287695528.16982.4.camel@heimdal.trondhjem.org \
    --to=trond.myklebust@netapp.com \
    --cc=iisaman@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.