On Wed, Sep 02, 2015 at 08:21:20AM +1000, Dave Chinner wrote:
Which means applications that should "just work" without
modification on DAX are now subtly broken and don't actually
guarantee data is safe after a crash. That's a pretty nasty
landmine, and goes against *everything* we've claimed about using
DAX with existing applications.
That's wrong, and needs fixing.
I agree that we need to fix fsync as well, and that the fsync solution could
be used to implement msync if we choose to go that route. I think we might
want to consider keeping the msync and fsync implementations separate, though,
for two reasons.
1) The current msync implementation is much more efficient than what will be
needed for fsync. Fsync will need to call into the filesystem, traverse all
the blocks, get kernel virtual addresses from those and then call
wb_cache_pmem() on those kernel addresses. I think this is a necessary evil
for fsync since you don't have a VMA, but for msync we do and we can just
flush using the user addresses without any fs lookups.
2) I believe that the near-term fsync code will rely on struct pages for
PMEM, which I believe are possible but optional as of Dan's last patch set:
I believe that this means that if we don't have struct pages for PMEM (becuase
ZONE_DEVICE et al. are turned off) fsync won't work. I'd be nice not to lose
msync as well.