From: Benny Halevy <bhalevy@panasas.com>
To: Fred Isaman <iisaman@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 00/12] RFC: pnfs: LAYOUTGRT/DEVINFO submission, v3
Date: Wed, 29 Sep 2010 12:59:10 +0200 [thread overview]
Message-ID: <4CA31BFE.7080101@panasas.com> (raw)
In-Reply-To: <1285193110-24073-1-git-send-email-iisaman@netapp.com>
Thanks!
I've released pnfs-all-2.6.36-rc6-2010-09-29 based on this patchset
and your rebase of pnfs-submit in bennys-pnfs-submit-on-devinfo-rc5.
I've made a few fixes on top of it and rebased everything else
on top of it (which was quite painful :)
I'll send the list of patches separately.
Benny
On 2010-09-23 00:04, Fred Isaman wrote:
> This fixes various issue brought up in comments to the previous version.
>
> Major changes are:
> bugfixes and renames in the deviceid cache
> fix Kconfig using a suggestion from Trond
> moved module_get to simplify and avoid bug in find_pnfs_driver_locked
>
> For those interested, the patches can also be found at
> git://linux-nfs.org/~iisaman/linux-pnfs.git,
> under the branch devinfo-submit-rc5-trond
>
> A rebase of Benny's pnfs-submit branch onto these patches is under
> the branch bennys-pnfs-submit-on-devinfo-rc5
>
>
>
>
>
> 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 chunks. This chunk 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
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-09-29 10:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 22:04 [PATCH 00/12] RFC: pnfs: LAYOUTGRT/DEVINFO submission, v3 Fred Isaman
2010-09-22 22:04 ` [PATCH 01/12] NFSD: remove duplicate NFS4_STATEID_SIZE Fred Isaman
2010-09-22 22:05 ` [PATCH 02/12] SUNRPC: define xdr_decode_opaque_fixed Fred Isaman
2010-09-22 22:05 ` [PATCH 03/12] RFC: pnfsd, pnfs: protocol level pnfs constants Fred Isaman
2010-09-22 22:05 ` [PATCH 04/12] RFC: nfs: change stateid to be a union Fred Isaman
2010-09-22 22:05 ` [PATCH 05/12] RFC: nfs: ask for layouttypes during fsinfo call Fred Isaman
2010-09-22 22:05 ` [PATCH 06/12] RFC: nfs: set layout driver Fred Isaman
2010-09-22 22:05 ` [PATCH 07/12] RFC: pnfs: full mount/umount infrastructure Fred Isaman
2010-09-22 22:05 ` [PATCH 08/12] RFC: pnfs: filelayout: introduce minimal file layout driver Fred Isaman
2010-09-22 22:05 ` [PATCH 09/12] RFC: nfs: create and destroy inode's layout cache Fred Isaman
2010-09-22 22:05 ` [PATCH 10/12] RFC: nfs: client needs to maintain list of inodes with active layouts Fred Isaman
2010-09-22 22:05 ` [PATCH 11/12] RFC: pnfs: add LAYOUTGET and GETDEVICEINFO infrastructure Fred Isaman
2010-09-22 22:05 ` [PATCH 12/12] RFC: pnfs: filelayout: add driver's " Fred Isaman
2010-09-29 10:59 ` Benny Halevy [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=4CA31BFE.7080101@panasas.com \
--to=bhalevy@panasas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).