diff options
author | Matias Bjørling <mb@lightnvm.io> | 2018-11-26 22:27:03 +0300 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2018-11-27 05:30:40 +0300 |
commit | ef78e5ec9214376c5cb989f5da70b02d0c117b66 (patch) | |
tree | d111e5e3d4565275b10f9394ac7da6a1389d1274 /fs/crypto | |
parent | 6f8b52ba442ce1372a58df4e85f169686ef52a0d (diff) | |
download | linux-ef78e5ec9214376c5cb989f5da70b02d0c117b66.tar.xz |
ia64: export node_distance function
The numa_slit variable used by node_distance is available to a
module as long as it is linked at compile-time. However, it is
not available to loadable modules. Leading to errors such as:
ERROR: "numa_slit" [drivers/nvme/host/nvme-core.ko] undefined!
The error above is caused by the nvme multipath code that makes
use of node_distance for its path calculation. When the patch was
added, the lightnvm subsystem would select nvme and always compile
it in, leading to the node_distance call to always succeed.
However, when this requirement was removed, nvme could be compiled
in as a module, which exposed this bug.
This patch extracts node_distance to a function and exports it.
Since ACPI is depending on node_distance being a simple lookup to
numa_slit, the previous behavior is exposed as slit_distance and its
users updated.
Fixes: f333444708f82 "nvme: take node locality into account when selecting a path"
Fixes: 73569e11032f "lightnvm: remove dependencies on BLK_DEV_NVME and PCI"
Signed-off-by: Matias Bjøring <mb@lightnvm.io>
Signed-off-by: Tony Luck <tony.luck@intel.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/crypto')
0 files changed, 0 insertions, 0 deletions