diff options
author | Dan Williams <dan.j.williams@intel.com> | 2017-05-29 16:12:20 -0400 |
---|---|---|
committer | Dan Williams <dan.j.williams@intel.com> | 2017-06-15 17:35:24 -0400 |
commit | 81f558701ae8d5677635118751b1b4043094c7e9 (patch) | |
tree | 6fc9fe36c0f0c073c13337e096cba143494bfbd0 /fs/dax.c | |
parent | 6318770a7d43a4166b6a8e3cef62e4a019d3c95e (diff) |
x86, dax: replace clear_pmem() with open coded memset + dax_ops->flush
The clear_pmem() helper simply combines a memset() plus a cache flush.
Now that the flush routine is optionally provided by the dax device
driver we can avoid unnecessary cache management on dax devices fronting
volatile memory.
With clear_pmem() gone we can follow on with a patch to make pmem cache
management completely defined within the pmem driver.
Cc: <x86@kernel.org>
Cc: Jeff Moyer <jmoyer@redhat.com>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Matthew Wilcox <mawilcox@microsoft.com>
Cc: Ross Zwisler <ross.zwisler@linux.intel.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'fs/dax.c')
-rw-r--r-- | fs/dax.c | 3 |
1 files changed, 2 insertions, 1 deletions
@@ -975,7 +975,8 @@ int __dax_zero_page_range(struct block_device *bdev, | |||
975 | dax_read_unlock(id); | 975 | dax_read_unlock(id); |
976 | return rc; | 976 | return rc; |
977 | } | 977 | } |
978 | clear_pmem(kaddr + offset, size); | 978 | memset(kaddr + offset, 0, size); |
979 | dax_flush(dax_dev, pgoff, kaddr + offset, size); | ||
979 | dax_read_unlock(id); | 980 | dax_read_unlock(id); |
980 | } | 981 | } |
981 | return 0; | 982 | return 0; |