public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@panasas.com>
To: Fred Isaman <iisaman@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/4]: Fix EAGAIN handling for the filelayout
Date: Mon, 14 Jun 2010 20:08:26 -0400	[thread overview]
Message-ID: <4C16C47A.3080305@panasas.com> (raw)
In-Reply-To: <1276460322-13873-1-git-send-email-iisaman@netapp.com>

On Jun. 13, 2010, 16:18 -0400, Fred Isaman <iisaman@netapp.com> wrote:
> These patches remove pnfs_call_done and all the routines associated with it.
> They were quite buggy for filelayout, and tended to crash the client anytime
> EAGAIN handling was invoked (in particular on short reads.)
> 
> The first patch just has filelayout avoid using them entirely. It should NOT
> be reverted in the post-submit.
> 
> The subsequent patches remove the unused code for pnfs-submit. It is
> expected they will be reverted in the post-submit.
> 
> Fred
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Merged at pnfs-all-2.6.35-rc3-2010-06-14 pnfs-submit
patches 2/4 to 4/4 reverted in pnfs post submit.

Thanks!

Benny

      parent reply	other threads:[~2010-06-15  0:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-13 20:18 [PATCH 0/4]: Fix EAGAIN handling for the filelayout Fred Isaman
2010-06-13 20:18 ` [PATCH 1/4] pnfs-submit: filelayout: Stop using pnfs_call_done and friends Fred Isaman
2010-06-13 20:18   ` [PATCH 2/4] pnfs-submit: Remove checks for non-rpc drivers Fred Isaman
2010-06-13 20:18     ` [PATCH 3/4] pnfs-submit: Remove pnfs_call_done and friends Fred Isaman
2010-06-13 20:18       ` [PATCH 4/4] pnfs-submit: Remove pnfs_error Fred Isaman
2010-06-15  0:08 ` Benny Halevy [this message]

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=4C16C47A.3080305@panasas.com \
    --to=bhalevy@panasas.com \
    --cc=iisaman@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