diff options
| author | Dan Williams <dan.j.williams@intel.com> | 2017-05-29 22:02:52 +0200 |
|---|---|---|
| committer | Dan Williams <dan.j.williams@intel.com> | 2017-06-15 23:34:59 +0200 |
| commit | abebfbe2f7315dd3ec9a0c69596a76e32beb5749 (patch) | |
| tree | e0b8a531424d7625e19a82a9151fa64a0a30671b /drivers/devfreq | |
| parent | dax, pmem: introduce an optional 'flush' dax_operation (diff) | |
| download | linux-abebfbe2f7315dd3ec9a0c69596a76e32beb5749.tar.xz linux-abebfbe2f7315dd3ec9a0c69596a76e32beb5749.zip | |
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>
Diffstat (limited to 'drivers/devfreq')
0 files changed, 0 insertions, 0 deletions