Re: [PATCH 2/2] nfs41: handle BLK_LAYOUT CB_RECALL_ANY

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2011-11-01 at 00:38 +0800, Peng Tao wrote: 
> On Mon, Oct 31, 2011 at 11:49 PM, Trond Myklebust
> <Trond.Myklebust@xxxxxxxxxx> 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.

No it doesn't. NFS4_OK means that the client acknowledges that it has
been given a new limit on the number of recallable objects it can keep.
There is no requirement in the text that it should send layoutreturn or
that the server should expect that.

In any case, there is no reason to make a difference between block,
object and file layouts when it comes to CB_RECALL_ANY. The code to
handle it should be the same for all.

-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@xxxxxxxxxx
www.netapp.com

--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux