From: Peng Tao <bergwolf@gmail.com>
To: benny@tonian.com
Cc: bharrosh@panasas.com, linux-nfs@vger.kernel.org
Subject: [PATCH v2 0/3] recoalesce when ld read/write fails
Date: Fri, 12 Aug 2011 18:00:10 -0700 [thread overview]
Message-ID: <1313197213-1651-1-git-send-email-bergwolf@gmail.com> (raw)
Hi,
I have moved the error handling inside mds_ops->rpc_release to reuse code
as suggested by Boaz.
I think we still need to issue the IO even for write because
we don't know if current writeback is the last one. So if we re-dirty the
pages and this is the last flush (flush at file close), then we don't have
a later flusher to writeback the re-dirtied pages. Boaz, please help see if
current approach is OK. Thanks.
The two cleanup patches (pipe upcall and set_lo_fail) are seperated out of
this patchset so they can be merged more easily.
Thanks,
Tao
Peng Tao (3):
pNFS: recoalesce when ld write pagelist fails
pNFS: recoalesce when ld read pagelist fails
pNFS: introduce pnfs private workqueue
fs/nfs/blocklayout/blocklayout.c | 17 +++++--
fs/nfs/objlayout/objio_osd.c | 8 +++
fs/nfs/objlayout/objlayout.c | 4 +-
fs/nfs/pnfs.c | 92 +++++++++++++++++++++++++++-----------
fs/nfs/pnfs.h | 8 +++-
fs/nfs/read.c | 13 +++++-
fs/nfs/write.c | 25 ++++++++++-
7 files changed, 129 insertions(+), 38 deletions(-)
next reply other threads:[~2011-08-16 13:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-13 1:00 Peng Tao [this message]
2011-08-13 1:00 ` [PATCH v2 1/3] pNFS: recoalesce when ld write pagelist fails Peng Tao
2011-08-23 14:45 ` Peng Tao
2011-08-27 2:43 ` Boaz Harrosh
2011-08-27 10:47 ` Peng Tao
2011-08-29 21:16 ` Boaz Harrosh
2011-08-13 1:00 ` [PATCH v2 2/3] pNFS: recoalesce when ld read " Peng Tao
2011-08-13 1:00 ` [PATCH v2 3/3] pNFS: introduce pnfs private workqueue Peng Tao
2011-08-16 20:43 ` [PATCH v2 0/3] recoalesce when ld read/write fails Boaz Harrosh
2011-08-17 13:42 ` Peng Tao
2011-08-22 23:24 ` Boaz Harrosh
2011-08-23 14:31 ` 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=1313197213-1651-1-git-send-email-bergwolf@gmail.com \
--to=bergwolf@gmail.com \
--cc=benny@tonian.com \
--cc=bharrosh@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).