diff options
| author | Dan Williams <dan.j.williams@intel.com> | 2019-11-12 17:13:31 -0800 |
|---|---|---|
| committer | Dan Williams <dan.j.williams@intel.com> | 2019-11-19 09:52:12 -0800 |
| commit | cb4dd729ee6ccc67ad604b1750990eb8c18783fa (patch) | |
| tree | afe0726ecd70122e58baa156626232a8e76e2242 /drivers/net/wan/farsync.c | |
| parent | bfd2e9140656a061138ecdc6a5485d5e2a7a3333 (diff) | |
| download | linux-cb4dd729ee6ccc67ad604b1750990eb8c18783fa.tar.gz linux-cb4dd729ee6ccc67ad604b1750990eb8c18783fa.tar.bz2 linux-cb4dd729ee6ccc67ad604b1750990eb8c18783fa.zip | |
dax: Add numa_node to the default device-dax attributes
It is confusing that device-dax instances publish a 'target_node'
attribute, but not a 'numa_node'. The 'numa_node' information is
available elsewhere in the sysfs device hierarchy, but it is not obvious
and not reliable from one device-dax instance-type (e.g. child devices
of nvdimm namespaces) to the next (e.g. 'hmem' devices defined by EFI
Specific Purpose Memory and the ACPI HMAT).
Cc: Ira Weiny <ira.weiny@intel.com>
Cc: Vishal Verma <vishal.l.verma@intel.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Reviewed-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
Link: https://lore.kernel.org/r/157309906102.1582359.4262088001244476001.stgit@dwillia2-desk3.amr.corp.intel.com
Diffstat (limited to 'drivers/net/wan/farsync.c')
0 files changed, 0 insertions, 0 deletions