From: Peng Tao <bergwolf@gmail.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: linux-nfs@vger.kernel.org, bhalevy@tonian.com,
Peng Tao <peng_tao@emc.com>
Subject: Re: [PATCH 2/2] nfs41: handle BLK_LAYOUT CB_RECALL_ANY
Date: Tue, 1 Nov 2011 00:38:35 +0800 [thread overview]
Message-ID: <CA+a=Yy4L4GDsQL6hHG4DRLNPmvkMBpk4mW9ofWbQob+z2a1G2A@mail.gmail.com> (raw)
In-Reply-To: <1320076148.4714.4.camel@lade.trondhjem.org>
On Mon, Oct 31, 2011 at 11:49 PM, Trond Myklebust
<Trond.Myklebust@netapp.com> wrote:
> On Mon, 2011-10-31 at 08:15 -0700, Peng Tao wrote:
>> For blocklayout, we need to issue layoutreturn to return layouts when
>> handling CB_RECALL_ANY.
>
> Why?
Because replying NFS4_OK to CB_RECALL_ANY indicates that client knows
that server wants client to return layout. And server will be waiting
for layoutreturn in such case.
Thanks,
Tao
>
> --
> Trond Myklebust
> Linux NFS client maintainer
>
> NetApp
> Trond.Myklebust@netapp.com
> www.netapp.com
>
>
next prev parent reply other threads:[~2011-10-31 16:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 15:15 [PATCH 1/2 RESEND] NFS4: fix cb_recallany decode error Peng Tao
2011-10-31 15:15 ` [PATCH 2/2] nfs41: handle BLK_LAYOUT CB_RECALL_ANY Peng Tao
2011-10-31 15:49 ` Trond Myklebust
2011-10-31 16:38 ` Peng Tao [this message]
2011-10-31 16:45 ` Trond Myklebust
2011-10-31 17:02 ` Peng Tao
2011-10-31 17:08 ` Benny Halevy
2011-10-31 17:42 ` Trond Myklebust
2011-10-31 17:57 ` Benny Halevy
2011-10-31 18:20 ` Trond Myklebust
2011-10-31 18:23 ` [nfsv4] " Matt W. Benjamin
2011-10-31 18:31 ` Trond Myklebust
2011-10-31 18:31 ` Jim Rees
2011-10-31 18:39 ` Trond Myklebust
2011-11-01 5:29 ` tao.peng
2011-11-04 1:33 ` tao.peng
2011-10-31 21:42 ` [nfsv4] " Welch, Brent
2011-11-01 14:59 ` david.noveck
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='CA+a=Yy4L4GDsQL6hHG4DRLNPmvkMBpk4mW9ofWbQob+z2a1G2A@mail.gmail.com' \
--to=bergwolf@gmail.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bhalevy@tonian.com \
--cc=linux-nfs@vger.kernel.org \
--cc=peng_tao@emc.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).