Linux NFS development
 help / color / mirror / Atom feed
From: Peng Tao <bergwolf@gmail.com>
To: linux-nfs@vger.kernel.org
Cc: rees@umich.edu, bhalevy@tonian.com, Trond.Myklebust@netapp.com
Subject: [PATCH-RFC 0/2] pNFS: recoalesce pages when ld read/write fails
Date: Sat,  6 Aug 2011 08:52:12 -0700	[thread overview]
Message-ID: <1312645934-4436-1-git-send-email-bergwolf@gmail.com> (raw)

Hi,

I start to look at the error handling for ld_read/write_done.
The two patches try to address the error handling for read/write pagelist
failures, via nfs readpage/writepage interface. Please see if this method
is proper. Thanks!

Cheers,
Tao


             reply	other threads:[~2011-08-06 15:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-06 15:52 Peng Tao [this message]
2011-08-06 15:52 ` [PATCH 1/2] pNFS: deal with ld write failure Peng Tao
2011-08-06 15:52 ` [PATCH 2/2] pNFS: deal with ld read failure Peng Tao
2011-08-08 14:33 ` [PATCH-RFC 0/2] pNFS: recoalesce pages when ld read/write fails Peng Tao
  -- strict thread matches above, loose matches on Subject: below --
2011-08-08 15: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=1312645934-4436-1-git-send-email-bergwolf@gmail.com \
    --to=bergwolf@gmail.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=bhalevy@tonian.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=rees@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