dax: introduce DAX_RECOVERY_WRITE dax access mode
Up till now, dax_direct_access() is used implicitly for normal access, but for the purpose of recovery write, dax range with poison is requested. To make the interface clear, introduce enum dax_access_mode { DAX_ACCESS, DAX_RECOVERY_WRITE, } where DAX_ACCESS is used for normal dax access, and DAX_RECOVERY_WRITE is used for dax recovery write. Suggested-by:Dan Williams <dan.j.williams@intel.com> Signed-off-by:
Jane Chu <jane.chu@oracle.com> Reviewed-by:
Christoph Hellwig <hch@lst.de> Cc: Mike Snitzer <snitzer@redhat.com> Reviewed-by:
Vivek Goyal <vgoyal@redhat.com> Link: https://lore.kernel.org/r/165247982851.52965.11024212198889762949.stgit@dwillia2-desk3.amr.corp.intel.com Signed-off-by:
Dan Williams <dan.j.williams@intel.com>
Showing
- drivers/dax/super.c 3 additions, 2 deletionsdrivers/dax/super.c
- drivers/md/dm-linear.c 3 additions, 2 deletionsdrivers/md/dm-linear.c
- drivers/md/dm-log-writes.c 3 additions, 2 deletionsdrivers/md/dm-log-writes.c
- drivers/md/dm-stripe.c 3 additions, 2 deletionsdrivers/md/dm-stripe.c
- drivers/md/dm-target.c 3 additions, 1 deletiondrivers/md/dm-target.c
- drivers/md/dm-writecache.c 4 additions, 3 deletionsdrivers/md/dm-writecache.c
- drivers/md/dm.c 3 additions, 2 deletionsdrivers/md/dm.c
- drivers/nvdimm/pmem.c 5 additions, 3 deletionsdrivers/nvdimm/pmem.c
- drivers/nvdimm/pmem.h 4 additions, 1 deletiondrivers/nvdimm/pmem.h
- drivers/s390/block/dcssblk.c 6 additions, 3 deletionsdrivers/s390/block/dcssblk.c
- fs/dax.c 5 additions, 4 deletionsfs/dax.c
- fs/fuse/dax.c 2 additions, 2 deletionsfs/fuse/dax.c
- fs/fuse/virtio_fs.c 4 additions, 2 deletionsfs/fuse/virtio_fs.c
- include/linux/dax.h 7 additions, 2 deletionsinclude/linux/dax.h
- include/linux/device-mapper.h 3 additions, 1 deletioninclude/linux/device-mapper.h
- tools/testing/nvdimm/pmem-dax.c 3 additions, 1 deletiontools/testing/nvdimm/pmem-dax.c
Loading
Please register or sign in to comment