diff options
| author | Jane Chu <jane.chu@oracle.com> | 2022-05-13 15:10:58 -0700 |
|---|---|---|
| committer | Dan Williams <dan.j.williams@intel.com> | 2022-05-16 13:35:56 -0700 |
| commit | e511c4a3d2a1f64aafc1f5df37a2ffcf7ef91b55 (patch) | |
| tree | eccb155ac340c8bd514ab14af30edfc48208b3bd /mm/mapping_dirty_helpers.c | |
| parent | 5898b43af954b83c4a4ee4ab85c4dbafa395822a (diff) | |
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>
Diffstat (limited to 'mm/mapping_dirty_helpers.c')
0 files changed, 0 insertions, 0 deletions