From: Matthew Wilcox [mailto:firstname.lastname@example.org]
Sent: Wednesday, May 16, 2018 12:20 AM>
> > > > Then there's the problem of reconnecting the page cache (which
> > > > pointed to by ephemeral data structures like inodes and dentries) to
> > > > the new inodes.
> > > Yes, it is not easy.
> > Right ... and until we have that ability, there's no point in this patch.
> We are focusing to realize this ability.
But is it the right approach? So far we have (I think) two parallel
activities. The first is for local storage, using DAX to store files
directly on the pmem. The second is a physical block cache for network
filesystems (both NAS and SAN). You seem to be wanting to supplant the
second effort, but I think it's much harder to reconnect the logical cache
(ie the page cache) than it is the physical cache (ie the block cache).
Thanks for correcting my idea with cache line.
But I have questions about that, assuming NVDIMM works with pmem mode, even we
used it as physical block cache, like dm-cache, there is potential risk with
this cache line issue, because NVDIMMs are bytes-address storage, right?
If system crash happens, that means CPU doesn't have opportunity to flush all dirty
data from cache lines to NVDIMM, during copying data pointed by bio_vec.bv_page to
I know there is btt which is used to guarantee sector atomic with block mode,
but for pmem mode that will likely cause mix of new and old data in one page
Correct me if anything wrong.
Another question, if we used NVDIMMs as physical block cache for network filesystems,
Does industry have existing implementation to bypass Page Cache similarly like DAX way,
that is to say, directly storing data to NVDIMMs from userspace, rather than copying
data from kernel space memory to NVDIMMs.