On Tue, Jul 23, 2024 at 9:17 AM Roland Mainz <roland.mainz@xxxxxxxxxxx> wrote: > > Hi! > > ---- > > [2nd attempt to send this email] > The Win32 API has |FILE_ATTRIBUTE_TEMPORARY| (see > https://learn.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-createfilea) > to optimise for short-lived/small temporary files - would it be useful > to reflect that in the NFSv4.2 protocol via a |FATTR4_TMPFILE| > attribute (sort of the opposite of |FATTR4_OFFLINE|, such a > |FATTR4_TMPFILE| should be ignored by HSM, and flushing to stable > storage should be relaxed/delayed as long as possible) ? I think a more appropriate medium for this message is an IETF NFSv4 mailing list as FATTR4_TMPFILE is not a spec attribute. > > ---- > > Bye, > Roland > -- > __ . . __ > (o.\ \/ /.o) roland.mainz@xxxxxxxxxxx > \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer > /O /==\ O\ TEL +49 641 3992797 > (;O/ \/ \O;) >
