On Fri, Jul 30, 2021 at 3:02 AM Shiyang Ruan <ruansy.fnst@xxxxxxxxxxx> wrote: > > Pmem device could be a target of mapped device. In order to find out > the global location on a mapped device, we introduce this to translate > offset from target device to mapped device. > > Currently, we implement it on linear target, which is easy to do the > translation. Other targets will be supported in the future. However, > some targets may not support it because of the non-linear mapping. > > Signed-off-by: Shiyang Ruan <ruansy.fnst@xxxxxxxxxxx> > --- > block/genhd.c | 56 +++++++++++++++++++++++++++++++++++ > drivers/md/dm-linear.c | 20 +++++++++++++ > include/linux/device-mapper.h | 5 ++++ > include/linux/genhd.h | 1 + > 4 files changed, 82 insertions(+) This might be where dax-device support needs to part ways with the block layer. As Christoph has mentioned before the long term goal for dax-devices (direct mapped byte-addressable media) is to have filesystems mount on them directly and abandon block-layer entanglements. This patch goes the opposite direct and adds more block layer infrastructure to support a dax-device need. Now, I'm not opposed to this moving forward, but I'm not sure block and DM maintainers will be excited about this additional maintenance burden. At the same time a lot of effort has been poured into dax-reflink and I want that support to move forward. So, my proposal while we figure out what to do about device-mapper rmap is to have fs_dax_register_holder() fail on device-mapper dax-devices until we get wider agreement amongst all involved that this is an additional burden worth carrying. In the meantime XFS on PMEM will see fs_dax_register_holder() succeed and DAX reflink support can be gated on whether the dax-device allowed the notify failure handler to be registered. Now, there may be room to allow reflink on device-mapper-dax for CONFIG_MEMORY_FAILURE=n builds, but that would collide with future work to use notify_failure for more than memory_failure, but also NVDIMM_REVALIDATE_POISON, and surprise memory-device-remove events. The code in this patch looks ok to me, just not the direction the dax-device layer was looking to go. It might be time to revive the discussions around support for concatenation and striping in the pmem driver itself, especially as the CXL label specification is already adding support for physically discontiguous namespaces. At a minimum if the patch set is organized to support XFS-reflink on PMEM-DAX and later XFS-reflink on DM-DAX some progress can be made without waiting for the whole set to be accepted.
