Dan Williams <dan.j.williams@xxxxxxxxx> writes: > On Wed, Jun 10, 2015 at 8:54 AM, Jeff Moyer <jmoyer@xxxxxxxxxx> wrote: >> Toshi Kani <toshi.kani@xxxxxx> writes: >> >>> Since NVDIMMs are installed on memory slots, they expose the NUMA >>> topology of a platform. This patchset adds support of sysfs >>> 'numa_node' to I/O-related NVDIMM devices under /sys/bus/nd/devices. >>> This enables numactl(8) to accept 'block:' and 'file:' paths of >>> pmem and btt devices as shown in the examples below. >>> numactl --preferred block:pmem0 --show >>> numactl --preferred file:/dev/pmem0s --show >>> >>> numactl can be used to bind an application to the locality of >>> a target NVDIMM for better performance. Here is a result of fio >>> benchmark to ext4/dax on an HP DL380 with 2 sockets for local and >>> remote settings. >>> >>> Local [1] : 4098.3MB/s >>> Remote [2]: 3718.4MB/s >>> >>> [1] numactl --preferred block:pmem0 --cpunodebind block:pmem0 fio <fs-on-pmem0> >>> [2] numactl --preferred block:pmem1 --cpunodebind block:pmem1 fio <fs-on-pmem0> >> >> Did you post the patches to numactl somewhere? >> > > numactl already supports this today. Ah, I did not know that. I guess I should have RTFM. :) Cheers, Jeff -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
