utimes ==> flush

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

 



Since utimes of a cached file could reset the file time before a write
is sent remotely, do NFS and the Linux cluster file systems simply
turn setattr of any timestamp into a fsync of all cached file data?
(this seems excessive when the file is cacheable/oplocked).   Is there
are precedent for caching the write of timestamps when writebehind
file data is cached (otherwise the performance penalty could be
horrible)?

-- 
Thanks,

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

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux