linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@panasas.com>
To: NFS list <linux-nfs@vger.kernel.org>
Subject: pnfs git tree status pnfs-all-3.0-2011-06-06
Date: Mon, 06 Jun 2011 14:57:33 -0400	[thread overview]
Message-ID: <4DED231D.8070304@panasas.com> (raw)

I've forward ported the spnfs and spnfs-block code to 2.6.39 and 3.0.

Totally untested yet, but it compiles beautifully :)
for spnfs-block's use, I moved fallocate back to inode_operations
as a temporary solution, despite of Christoph's reservations
as this is not hitting mainline anytime soon.

respective tips are at
pnfs-all-2.6.39 pnfs-all-2.6.39-2011-06-06
pnfs-all-latest pnfs-all-3.0-2011-06-06

patches since 2011-05-31:

pnfs-all-2.6.39:
03adb44 NFS: fix umount of pnfs filesystems
f4d5c0c FIXME: spnfs cummulative patch
d6d442f SQUASHME: spnfs: use kern_path rather than path_lookup
4938a27 FIXME: spnfs-block: restore i_op->fallocate
4ce3376 FIXME: spnfs-block: pNFS block layout server implementation
cummulative patch

nfs-upstream:
cf1eb60 NFS: fix umount of pnfs filesystems

spnfs-all:
f4d5c0c FIXME: spnfs cummulative patch
d6d442f SQUASHME: spnfs: use kern_path rather than path_lookup

spnfs-block-all:
4938a27 FIXME: spnfs-block: restore i_op->fallocate
4ce3376 FIXME: spnfs-block: pNFS block layout server implementation
cummulative patch

             reply	other threads:[~2011-06-06 18:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-06 18:57 Benny Halevy [this message]
2011-06-28  7:57 ` pnfs git tree status pnfs-all-3.0-rc5-2011-06-28 Benny Halevy

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=4DED231D.8070304@panasas.com \
    --to=bhalevy@panasas.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).