To guarantee metadata consistency, applications will manually call many fsyncs after mmap with MAP_SYNC failed, as shown by this issue in pmdk. But in NOVA, metadata can be kept consistent without fsync or MAP_SYNC, so the fsyncs generated by applications are redundant and significantly decrease performance.
So, I think to support MAP_SYNC and ignore it can match better with the behavior of other DAX-supporting file systems, as stated by this comment.
To guarantee metadata consistency, applications will manually call many
fsync
s aftermmap
withMAP_SYNC
failed, as shown by this issue in pmdk. But in NOVA, metadata can be kept consistent withoutfsync
orMAP_SYNC
, so thefsync
s generated by applications are redundant and significantly decrease performance. So, I think to support MAP_SYNC and ignore it can match better with the behavior of other DAX-supporting file systems, as stated by this comment.