diff options
author | 2018-11-07 15:31:23 -0800 | |
---|---|---|
committer | 2019-01-06 21:41:55 -0800 | |
commit | d200781ef237a354d918ceff5cee350d88a93d42 (patch) | |
tree | afd53c6e25a57e31b8c0c8542e086bd50840bc9a /tools/perf/scripts/python/export-to-sqlite.py | |
parent | device-dax: Move resource pinning+mapping into the common driver (diff) | |
download | linux-rng-d200781ef237a354d918ceff5cee350d88a93d42.tar.xz linux-rng-d200781ef237a354d918ceff5cee350d88a93d42.zip |
device-dax: Add support for a dax override driver
Introduce the 'new_id' concept for enabling a custom device-driver attach
policy for dax-bus drivers. The intended use is to have a mechanism for
hot-plugging device-dax ranges into the page allocator on-demand. With
this in place the default policy of using device-dax for performance
differentiated memory can be overridden by user-space policy that can
arrange for the memory range to be managed as 'System RAM' with
user-defined NUMA and other performance attributes.
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions