From: Toshi Kani <toshi.kani@hp.com>
To: rjw@rjwysocki.net, dan.j.williams@intel.com
Cc: linux-acpi@vger.kernel.org, linux-nvdimm@ml01.01.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/3] Add NUMA support for NVDIMM devices
Date: Fri, 19 Jun 2015 12:18:31 -0600 [thread overview]
Message-ID: <1434737914-18466-1-git-send-email-toshi.kani@hp.com> (raw)
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. A result of fio benchmark to ext4/dax
on an HP DL380 with 2 sockets for local & remote settings is shown
below.
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>
Patch 1/3 applies on top of the acpica branch of the pm tree.
Patch 2/3-3/3 apply on top of Dan Williams's patch series
"libnvdimm: ->rw_bytes(), BLK-mode, unit tests, and misc features".
---
v3:
- Update the comment of acpi_map_pxm_to_online_node(). (Rafael Wysocki)
v2:
- Add acpi_map_pxm_to_online_node(), which returns an online node.
- Manage visibility of sysfs numa_node with is_visible. (Dan Williams)
- Check ACPI_NFIT_PROXIMITY_VALID in spa->flags.
---
Toshi Kani (3):
1/3 acpi: Add acpi_map_pxm_to_online_node()
2/3 libnvdimm: Set numa_node to NVDIMM devices
3/3 libnvdimm: Add sysfs numa_node to NVDIMM devices
---
drivers/acpi/nfit.c | 7 ++++++
drivers/acpi/numa.c | 50 ++++++++++++++++++++++++++++++++++++++---
drivers/nvdimm/btt.c | 2 ++
drivers/nvdimm/btt_devs.c | 1 +
drivers/nvdimm/bus.c | 30 +++++++++++++++++++++++++
drivers/nvdimm/namespace_devs.c | 1 +
drivers/nvdimm/nd.h | 1 +
drivers/nvdimm/region.c | 1 +
drivers/nvdimm/region_devs.c | 1 +
include/linux/acpi.h | 5 +++++
include/linux/libnvdimm.h | 2 ++
11 files changed, 98 insertions(+), 3 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2015-06-19 18:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 18:18 Toshi Kani [this message]
2015-06-19 18:18 ` [PATCH v3 1/3] acpi: Add acpi_map_pxm_to_online_node() Toshi Kani
2015-06-19 23:26 ` Rafael J. Wysocki
2015-06-19 23:11 ` Toshi Kani
2015-06-19 18:18 ` [PATCH v3 2/3] libnvdimm: Set numa_node to NVDIMM devices Toshi Kani
2015-06-24 16:50 ` Dan Williams
2015-06-24 17:05 ` Toshi Kani
2015-06-24 17:08 ` Dan Williams
2015-06-24 17:14 ` Toshi Kani
2015-06-19 18:18 ` [PATCH v3 3/3] libnvdimm: Add sysfs " Toshi Kani
2015-06-19 20:01 ` Brice Goglin
2015-06-19 20:16 ` Toshi Kani
2015-06-24 0:26 ` Dan Williams
2015-06-24 0:36 ` Dan Williams
2015-06-24 16:38 ` Toshi Kani
2015-06-24 16:42 ` Dan Williams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1434737914-18466-1-git-send-email-toshi.kani@hp.com \
--to=toshi.kani@hp.com \
--cc=dan.j.williams@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=rjw@rjwysocki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®