All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@panasas.com>
To: NFS list <linux-nfs@vger.kernel.org>
Cc: Steve Dickson <steved@redhat.com>, Andy Adamson <andros@netapp.com>
Subject: pnfs git tree status pnfs-all-2.6.34-2010-05-17
Date: Mon, 17 May 2010 23:45:48 +0300	[thread overview]
Message-ID: <4BF1AAFC.7000308@panasas.com> (raw)
In-Reply-To: <4BE3315C.9090908@panasas.com>

Hi,

The pnfs tree is now rebased onto the fresh Linux 2.6.34.
Many thanks to Andy's for squashing many cleanup patches in pnfs-submit
and to the contributors listed below of course!

I released the following today:

pnfs-all-2.6.34-2010-05-17

As usual, cumulative patches can be generated from
git://linux-nfs.org/~bhalevy/linux-pnfs.git
using
git diff v2.6.34 pnfs-all-2.6.34-2010-05-17

Or, they can be downloaded from the wiki at:
http://wiki.linux-nfs.org/wiki/index.php/PNFS_Development_Git_tree

Latest patches (since 2010-05-06):

pnfs-submit:
Andy Adamson (14):
      SQUASHME pnfs_submit: move unmount_pnfs_layoutdriver call
      SQUASHME pnfs_submit: remove filelayout get threshold
      SQUASHME pnfs_submit: don't use pnfs_use_read
      SQUASHME pnfs_submit: don't use pnfs_use_write
      SQUASHME pnfs_submit: don't use pnfs_use_write for commit
      SQUASHME pnfs_submit: don't use pg_threshold
      SQUASHME pnfs_submit: remove pg_threshold
      SQUASHME pnfs_submit: don't use below_threshold in read
      SQUASHME pnfs_submit: don't use below_threshold in direct io
      SQUASHME pnfs_submit: remove unused threshold calculations
      SQUASHME pnfs_submit: cleanup filelayout pg_test
      SQUASHME pnfs_submit: use MDS session for dual MDS/DS
      SQUASHME pnfs_submit: update DS nfs4_set_client
      SQUASHME pnfs_submit: cleanup DS exchange flag processing

Benny Halevy (2):
      pnfs: async layout return
      SQUASHME: pnfs-submit: check for NULL nfs_client in nfs4_init_pnfs

Zhang Jingwang (3):
      SQUASHME: pnfs-submit: set pnfs_curr_ld before calling initialize_mountpoint
      SQUASHME: pnfs-submit: send layoutcommit until IO completed when return layout
      pnfs: devide put_lseg and return_layout_barrier into different workqueue

pnfs-block:
Benny Halevy (1):
      SQUASHME: pnfs-block: get rid of threshold policy ops

Tao Guo (2):
      pnfsblock: expose block_class interface
      pnfsblock: iterating all local block disks instead of only scsi disks when initializing mount point.

Zhang Jingwang (3):
      SQAUSHME: blocklayoutdriver: NULL pointer reference when committing too many extents
      pnfsblock: Lookup list entry of layouts and tags in reverse order
      SQUASHME: pnfs-block: set pnfs_blksize before calling set_pnfs_layoutdriver

pnfs-obj-all:
Benny Halevy (1):
      SQUASHME: pnfs-obj: get rid of threshold policy ops


  reply	other threads:[~2010-05-17 20:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-29 17:16 pnfs git tree status 2010-04-29 Benny Halevy
2010-05-06 21:13 ` pnfs git tree status pnfs-all-2.6.34-rc6-2010-05-06 pnfs-all-2.6.33-2010-05-06 Benny Halevy
2010-05-06 21:15   ` Benny Halevy
2010-05-17 20:45     ` Benny Halevy [this message]
2010-07-01 18:57       ` pnfs git tree status pnfs-all-2.6.34-2010-07-01 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=4BF1AAFC.7000308@panasas.com \
    --to=bhalevy@panasas.com \
    --cc=andros@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=steved@redhat.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 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.