From: Peng Tao <bergwolf@gmail.com>
To: Trond.Myklebust@netapp.com
Cc: linux-nfs@vger.kernel.org, mdw@umich.edu, honey@citi.umich.edu
Subject: [PATCH RESEND 0/9] pnfsblock patches for 3.3 post-rc1
Date: Tue, 10 Jan 2012 22:30:26 +0800 [thread overview]
Message-ID: <1326205835-2011-1-git-send-email-bergwolf@gmail.com> (raw)
Hi Trond,
These are pnfsblock patches rebased on top of nfs-for-3.3. All patches were sent to list before and merged by Benny.
Thanks,
Tao
Peng Tao (9):
pnfsblock: cleanup bl_mark_sectors_init
pnfsblock: acquire im_lock in _preload_range
pnfsblock: move find lock page logic out of bl_write_pagelist
pnfsblock: set read/write tk_status to pnfs_error
pnfsblock: remove rpc_call_ops from struct parallel_io
pnfsblock: clean up _add_entry
pnfsblock: alloc short extent before submit bio
pnfsblock: don't spinlock when freeing block_dev
pnfsblock: limit bio page count
fs/nfs/blocklayout/blocklayout.c | 202 ++++++++++++++++++++++++-------------
fs/nfs/blocklayout/blocklayout.h | 12 ++-
fs/nfs/blocklayout/extents.c | 176 ++++++++++++++-------------------
3 files changed, 215 insertions(+), 175 deletions(-)
next reply other threads:[~2012-01-10 14:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 14:30 Peng Tao [this message]
2012-01-10 14:30 ` [PATCH RESEND 1/9] pnfsblock: cleanup bl_mark_sectors_init Peng Tao
2012-01-10 14:30 ` [PATCH RESEND 3/9] pnfsblock: move find lock page logic out of bl_write_pagelist Peng Tao
2012-01-10 14:30 ` [PATCH RESEND 4/9] pnfsblock: set read/write tk_status to pnfs_error Peng Tao
2012-01-10 14:30 ` [PATCH RESEND 5/9] pnfsblock: remove rpc_call_ops from struct parallel_io Peng Tao
2012-01-10 14:30 ` [PATCH RESEND 6/9] pnfsblock: clean up _add_entry Peng Tao
2012-01-10 14:30 ` [PATCH RESEND 7/9] pnfsblock: alloc short extent before submit bio Peng Tao
2012-01-10 16:14 ` [PATCH RESEND 0/9] pnfsblock patches for 3.3 post-rc1 Jim Rees
2012-01-10 16:35 ` Peng Tao
2012-01-11 19:44 ` Trond Myklebust
2012-01-12 15:09 ` Peng Tao
2012-01-11 19:47 ` Trond Myklebust
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=1326205835-2011-1-git-send-email-bergwolf@gmail.com \
--to=bergwolf@gmail.com \
--cc=Trond.Myklebust@netapp.com \
--cc=honey@citi.umich.edu \
--cc=linux-nfs@vger.kernel.org \
--cc=mdw@umich.edu \
/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).