From: Chuck Lever <chuck.lever@oracle.com>
To: Frank Filz <ffilzlnx@us.ibm.com>
Cc: Trond Myklebust <trond.myklebust@netapp.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 0/4] Refactor data structures to support NFSv4 migration (2)
Date: Fri, 4 Mar 2011 17:57:34 -0500 [thread overview]
Message-ID: <FBE2594D-16CC-4A57-A74C-7A37AD578CFF@oracle.com> (raw)
In-Reply-To: <1299278738.5341.0.camel-LVD8ZR29O+mrIzol8Bc5pA@public.gmane.org>
On Mar 4, 2011, at 5:45 PM, Frank Filz wrote:
>
> Chuck, Trond,
>
> What is the outlook for the client patchset for migration?
Trond and I are going to meet next week to go over the prototype and roadmap. I'll post something for people to review soon. Client-side migration will likely go in 2.6.40, but that's up to Trond.
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
prev parent reply other threads:[~2011-03-04 22:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-24 1:32 [PATCH 0/4] Refactor data structures to support NFSv4 migration (2) Chuck Lever
2010-12-24 1:32 ` [PATCH 1/4] NFS: Allow walking nfs_client.cl_superblocks list outside client.c Chuck Lever
2010-12-24 1:32 ` [PATCH 2/4] NFS: Move cl_state_owners and related fields to the nfs_server struct Chuck Lever
2010-12-24 1:32 ` [PATCH 3/4] NFS: Introduce nfs_detach_delegations() Chuck Lever
2010-12-24 1:33 ` [PATCH 4/4] NFS: Move cl_delegations to the nfs_server struct Chuck Lever
[not found] ` <20101224012636.2445.41411.stgit-RytpoXr2tKZ9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2011-03-04 22:45 ` [PATCH 0/4] Refactor data structures to support NFSv4 migration (2) Frank Filz
[not found] ` <1299278738.5341.0.camel-LVD8ZR29O+mrIzol8Bc5pA@public.gmane.org>
2011-03-04 22:57 ` Chuck Lever [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=FBE2594D-16CC-4A57-A74C-7A37AD578CFF@oracle.com \
--to=chuck.lever@oracle.com \
--cc=ffilzlnx@us.ibm.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@netapp.com \
/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).