From: Peng Tao <bergwolf@gmail.com>
To: Trond.Myklebust@netapp.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/9] pnfsblock patches
Date: Fri, 2 Dec 2011 20:46:14 -0800 [thread overview]
Message-ID: <1322887583-2719-1-git-send-email-bergwolf@gmail.com> (raw)
Hi, Trond,
Following are some bugfix and improvements for blocklayout driver. All have been
sent to the list before and have been tested for several weeks.
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:[~2011-11-29 16:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 4:46 Peng Tao [this message]
2011-11-29 18:44 ` [PATCH 0/9] pnfsblock patches Jim Rees
2011-11-30 2:37 ` tao.peng
2011-11-30 13:05 ` Benny Halevy
2011-11-30 13:25 ` Peng Tao
2011-11-29 21:38 ` Boaz Harrosh
2011-11-29 22:58 ` Jim Rees
2011-11-29 23:39 ` Boaz Harrosh
2011-11-30 2:44 ` tao.peng
2011-12-03 4:46 ` [PATCH 1/9] pnfsblock: cleanup bl_mark_sectors_init Peng Tao
2011-12-03 4:46 ` [PATCH 3/9] pnfsblock: move find lock page logic out of bl_write_pagelist Peng Tao
2011-12-03 4:46 ` [PATCH 4/9] pnfsblock: set read/write tk_status to pnfs_error Peng Tao
2011-12-03 4:46 ` [PATCH 5/9] pnfsblock: remove rpc_call_ops from struct parallel_io Peng Tao
2011-12-03 4:46 ` [PATCH 6/9] pnfsblock: clean up _add_entry Peng Tao
2011-12-03 4:46 ` [PATCH 7/9] pnfsblock: alloc short extent before submit bio Peng Tao
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=1322887583-2719-1-git-send-email-bergwolf@gmail.com \
--to=bergwolf@gmail.com \
--cc=Trond.Myklebust@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).