From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Ricardo Labiaga <Ricardo.Labiaga@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [Patch 0/4] RECLAIM_COMPLETE functionality
Date: Sat, 05 Dec 2009 15:51:01 -0500 [thread overview]
Message-ID: <1260046261.29208.10.camel@localhost> (raw)
In-Reply-To: <1260044428-16341-1-git-send-email-Ricardo.Labiaga@netapp.com>
On Sat, 2009-12-05 at 12:20 -0800, Ricardo Labiaga wrote:
> The following patches implement RECLAIM_COMPLETE functionality to
> indicate completion of _global_ reclaims for the client. They do
> not yet implement RECLAIM_COMPLETE for file system migration.
>
> [PATCH 1/4] Cleanup some NFSv4 XDR decode comments
> [PATCH 2/4] nfs41: RECLAIM_COMPLETE XDR functionality
> [PATCH 3/4] nfs41: RECLAIM_COMPLETE functionality
> [PATCH 4/4] nfs41: Invoke RECLAIM_COMPLETE
>
> A separate patch will be mailed to Bruce to integrate skeleton
> functionality on the server side.
>
> The patches apply to Trond's master branch. They were tested on
> top of an old version of Andy's session draining patches, and
> the previous state reclaim bug fix series.
Applied. Thanks Ricardo...
prev parent reply other threads:[~2009-12-05 20:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-05 20:20 [Patch 0/4] RECLAIM_COMPLETE functionality Ricardo Labiaga
2009-12-05 20:20 ` [PATCH 1/4] Cleanup some NFSv4 XDR decode comments Ricardo Labiaga
2009-12-05 20:20 ` [PATCH 2/4] nfs41: RECLAIM_COMPLETE XDR functionality Ricardo Labiaga
2009-12-05 20:20 ` [PATCH 3/4] nfs41: RECLAIM_COMPLETE functionality Ricardo Labiaga
2009-12-05 20:20 ` [PATCH 4/4] nfs41: Invoke RECLAIM_COMPLETE Ricardo Labiaga
2009-12-05 20:51 ` Trond Myklebust [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=1260046261.29208.10.camel@localhost \
--to=trond.myklebust@netapp.com \
--cc=Ricardo.Labiaga@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