From: Alexander Duyck Date: Tue, 22 Jan 2019 18:39:47 +0000 (-0800) Subject: libnvdimm: Schedule device registration on node local to the device X-Git-Tag: v5.4-rc1~1511^2~36 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=af87b9a7863c7bb47f8bd015c0ce4a37d70c5225;p=platform%2Fkernel%2Flinux-rpi.git libnvdimm: Schedule device registration on node local to the device Force the device registration for nvdimm devices to be closer to the actual device. This is achieved by using either the NUMA node ID of the region, or of the parent. By doing this we can have everything above the region based on the region, and everything below the region based on the nvdimm bus. By guaranteeing NUMA locality I see an improvement of as high as 25% for per-node init of a system with 12TB of persistent memory. Reviewed-by: Bart Van Assche Signed-off-by: Alexander Duyck Signed-off-by: Greg Kroah-Hartman --- diff --git a/drivers/nvdimm/bus.c b/drivers/nvdimm/bus.c index dca5f7a..7bbff0a 100644 --- a/drivers/nvdimm/bus.c +++ b/drivers/nvdimm/bus.c @@ -23,6 +23,7 @@ #include #include #include +#include #include #include #include @@ -534,11 +535,15 @@ void __nd_device_register(struct device *dev) set_dev_node(dev, to_nd_region(dev)->numa_node); dev->bus = &nvdimm_bus_type; - if (dev->parent) + if (dev->parent) { get_device(dev->parent); + if (dev_to_node(dev) == NUMA_NO_NODE) + set_dev_node(dev, dev_to_node(dev->parent)); + } get_device(dev); - async_schedule_domain(nd_async_device_register, dev, - &nd_async_domain); + + async_schedule_dev_domain(nd_async_device_register, dev, + &nd_async_domain); } void nd_device_register(struct device *dev)