Re: [nfsv4] parallel LAYOUTGETs using open stateid

On 2010-10-07 09:50, Benny Halevy wrote:
> On Thu, Oct 7, 2010 at 9:21 AM, Fred Isaman <iisaman@citi.umich.edu> wrote:
>> This question came up as I was going through our layout stateid code.
>>
>> Can the client send multiple LAYOUTGETs in parallel before getting a
>> layoutstateid by using an open stateid?
>> If so, what is the server response?  The spec is not clear, but I
>> would assume it would do one of:
>> a) returning an error (what error?) on all but the first LAYOUTGET it sees
>> b) matching the openstateid to the layoutstateid it has already given
>> out and sending a reply with that stateid and a bumped seqid
> 
> I'm in favour of (b).

Just to clarify, what matters in this case is the returned logr_stateid
and seqid while the sent loga_stateid does not matter much.
If there's a pending layout recall on the server which has not been
completed by a matching LAYOUTRETURN the server can safely assume
that the layoutget was sent before the client received the CB_LAYOUTRECALL
and return NFS4ERR_RECALLCONFLICT.

Benny

> Are there any problems you see in that approach?
> 
> Benny
> 
>> Fred
>> _______________________________________________
>> nfsv4 mailing list
>> nfsv4@ietf.org
>> https://www.ietf.org/mailman/listinfo/nfsv4
>>
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4