| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 10 Jun 2015 11:54:38 -0400 From: Jeff Moyer <jmoyer@...hat.com> To: Toshi Kani <toshi.kani@...com> Cc: rjw@...ysocki.net, dan.j.williams@...el.com, linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org, linux-nvdimm@...1.01.org Subject: Re: [PATCH v2 0/3] Add NUMA support for NVDIMM devices Toshi Kani <toshi.kani@...com> 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? -Jeff -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists