Dan Williams abebfbe2f7 dm: add ->flush() dax operation support ... Allow device-mapper to route flush operations to the per-target implementation. In order for the device stacking to work we need a dax_dev and a pgoff relative to that device. This gives each layer of the stack the information it needs to look up the operation pointer for the next level. This conceptually allows for an array of mixed device drivers with varying flush implementations. Reviewed-by: Toshi Kani <toshi.kani@hpe.com> Reviewed-by: Mike Snitzer <snitzer@redhat.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com>		2017-06-15 14:34:59 -07:00
..
dax-private.h	Merge branch 'for-4.12/dax' into libnvdimm-for-next	2017-05-04 23:38:43 -07:00
dax.h	pmem: add dax_operations support	2017-04-19 15:14:35 -07:00
device-dax.h	dax: refactor dax-fs into a generic provider of 'struct dax_device' instances	2017-04-12 21:59:14 -07:00
device.c	Merge branch 'for-4.12/dax' into libnvdimm-for-next	2017-05-04 23:38:43 -07:00
Kconfig	device-dax: kill NR_DEV_DAX	2017-05-09 09:08:22 -07:00
Makefile	dax: refactor dax-fs into a generic provider of 'struct dax_device' instances	2017-04-12 21:59:14 -07:00
pmem.c	libnvdimm for 4.12	2017-05-05 18:49:20 -07:00
super.c	dm: add ->flush() dax operation support	2017-06-15 14:34:59 -07:00