diff options
author | Dan Williams <dan.j.williams@intel.com> | 2017-01-25 05:44:18 +0300 |
---|---|---|
committer | Dan Williams <dan.j.williams@intel.com> | 2017-04-20 01:14:35 +0300 |
commit | 6568b08b77816cda2a95919c7494108d983d5941 (patch) | |
tree | cdc776afdf8dd6c583155d169017eb78ab94a8bf /crypto | |
parent | 72058005411ffddcae6c06f7b691d635489132af (diff) | |
download | linux-6568b08b77816cda2a95919c7494108d983d5941.tar.xz |
dax: introduce dax_operations
Track a set of dax_operations per dax_device that can be set at
alloc_dax() time. These operations will be used to stop the abuse of
block_device_operations for communicating dax capabilities to
filesystems. It will also be used to replace the "pmem api" and move
pmem-specific cache maintenance, and other dax-driver-specific
filesystem-dax operations, to dax device methods. In particular this
allows us to stop abusing __copy_user_nocache(), via memcpy_to_pmem(),
with a driver specific replacement.
This is a standalone introduction of the operations. Follow on patches
convert each dax-driver and teach fs/dax.c to use ->direct_access() from
dax_operations instead of block_device_operations.
Suggested-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions