Subject: Re: [nfsv4] pNFS issue 9: last_write_offset

From: Benny Halevy <[email-masked]>
Date: Mon, 05 Jun 2006 08:34:37 +0300

Garth, the change looks good.  I'd consider deleting "Note: 
" though...

Benny

Garth Goodson wrote:
> Some text to make the changes described in issue 9.
> 
> http://www.nfsv4-editor.org/cgi-bin/roundup/nfsv4/issue9
> 
> 
> 14.4.2.  LAYOUTCOMMIT and size
> 
>    The file's size may be updated at LAYOUTCOMMIT time as well.  The
>    LAYOUTCOMMIT operation contains an argument ("last_write_offset")
>    that indicates the highest byte offset written but not yet
>    committed via LAYOUTCOMMIT.  Note: this argument is switched on a
>    boolean value indicating whether or not a previous write occured.  If
>    the switch is false, no "last_write_offset" is given; a
>    "last_write_offset" specifying an offset of 0 means byte 0 was the
>    highest last byte written.
> 
> ...
> 
> 22.46.2.  ARGUMENT
> 
>    union newoffset4 switch (bool newoffset) {
>        case TRUE:
>            offset4           offset;
>        case FALSE:
>            void;
>    };
> 
>    ...
> 
>    struct LAYOUTCOMMIT4args {
>        /* CURRENT_FH: file */
>        clientid4               clientid;
>        offset4                 offset;
>        length4                 length;
>        bool                    reclaim;
>        newoffset4              last_write_offset;
>        newtime4                time_modify;
>        newtime4                time_access;
>        pnfs_layoutupdate4      layoutupdate;
>    };
> 
> _______________________________________________
> nfsv4 mailing list
> [email-masked]
> https://www1.ietf.org/mailman/listinfo/nfsv4

_______________________________________________
nfsv4 mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/nfsv4