Re: [nfsv4] Fwd: New Version Notification for draft-haynes-nfsv4-layoutwcc-01.txt

["Mkrtchyan, Tigran" <[e-mail]>]

Hi Tom,

Thanks for the update. I have two comments:

1.

The introductions talk mostly about nfsv3-based flexfile layout. However, even
strongly coupled v4-based implementations will benefit from such functionality,
as attribute synchronization can be delegated to the client (fsync vs fdatasync).

2.
the paragraph:

"""
Each NFSv3 operation corresponds to one round trip between the client and server. So a WRITE followed by a GETATTR would require two round trips. In that scenario, the attribute information retrieved is considered to be strict server-client consistency. For NFSv4, the WRITE and GETATTR can be issued together inside a compound, which only requires one round trip between the client and server. And this is also considered to be a strict server-client consistency. In essence, the NFSv4 READ and WRITE operations drop the post-operation attributes, allowing the client to decide if it needs that information.
"""

Is still wrong for nfsv4, as on the data path we can't have READ/WRITE + GETATTR. I am not saying that we should change the pnfs protocol,
but the text might say that LAYOUT_WCC gives an opportunity for nfsv3 (and might be for later implementations) to make use of it.


Best regards,
   Tigran.


----- Original Message -----
> From: "Thomas Haynes" <[e-mail]>
> To: "NFSv4" <[e-mail]>
> Sent: Monday, 20 February, 2023 16:48:45
> Subject: [nfsv4] Fwd: New Version Notification for draft-haynes-nfsv4-layoutwcc-01.txt

> This version addresses the issue that the draft is NFSv3 Flex Files only.
> 
> Thanks,
> Tom
> 
> Begin forwarded message:
> 
> From: [e-mail]
> Subject: New Version Notification for draft-haynes-nfsv4-layoutwcc-01.txt
> Date: February 20, 2023 at 7:46:54 AM PST
> To: "Thomas Haynes" <[e-mail]>, "Trond Myklebust"
> <[e-mail]>
> 
> 
> A new version of I-D, draft-haynes-nfsv4-layoutwcc-01.txt
> has been successfully submitted by Thomas Haynes and posted to the
> IETF repository.
> 
> Name: draft-haynes-nfsv4-layoutwcc
> Revision: 01
> Title: Add LAYOUT_WCC to NFSv4.2
> Document date: 2023-02-20
> Group: Individual Submission
> Pages: 9
> URL:
> https://www.ietf.org/archive/id/draft-haynes-nfsv4-layoutwcc-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-haynes-nfsv4-layoutwcc/
> Html:
> https://www.ietf.org/archive/id/draft-haynes-nfsv4-layoutwcc-01.html
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-haynes-nfsv4-layoutwcc
> Diff:
> https://author-tools.ietf.org/iddiff?url2=draft-haynes-nfsv4-layoutwcc-01
> 
> Abstract:
>  The Parallel Network File System (pNFS) Flexible File Layout allows
>  for a file's metadata (MDS) and data (DS) to be on different servers.
>  It does not provide a mechanism for the data server to update the
>  metadata server of changes to the data part of the file.  The client
>  has knowledge of such updates, but lacks the ability to update the
>  metadata server.  This document presents a refinement to RFC8434 to
>  allow the client to update the metadata server to changes on the data
>  server.
> 
> 
> 
> 
> The IETF Secretariat
> 
> 
> 
> 
> _______________________________________________
> nfsv4 mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/nfsv4