On Tue, Jan 17, 2017 at 9:25 PM, <[email protected]> wrote: > On Fri, Jan 13, 2017 at 05:20:08PM -0700, Ross Zwisler wrote: >> We still have a lot of work to do, though, and I'd like to propose a >> discussion >> around what features people would like to see enabled in the coming year as >> well as what what use cases their customers have that we might not be aware >> of. > > +1 to the discussion > >> - Jan suggested [2] that we could use the radix tree as a cache to service >> DAX >> faults without needing to call into the filesystem. Are there any issues >> with this approach, and should we move forward with it as an optimization? > > Ahem. I believe I proposed this at last year's LSFMM. And I sent > patches to start that work. And Dan blocked it. So I'm not terribly > amused to see somebody else given credit for the idea. >
I "blocked" moving the phys to virt translation out of the driver since that mapping lifetime is device specific. However, I think caching the file offset to physical sector/address result is a great idea. _______________________________________________ Linux-nvdimm mailing list [email protected] https://lists.01.org/mailman/listinfo/linux-nvdimm
