From: Toshi Kani <toshi.kani@hp.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux ACPI <linux-acpi@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Rafael J Wysocki <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH v2 0/3] Add NUMA support for NVDIMM devices
Date: Thu, 11 Jun 2015 09:45:50 -0600 [thread overview]
Message-ID: <1434037550.11808.10.camel@misato.fc.hp.com> (raw)
In-Reply-To: <CAPcyv4jJv1df39W9YjP3FCeZDzZKOsV70xK9gbteykEUJVyDwQ@mail.gmail.com>
On Thu, 2015-06-11 at 08:38 -0700, Dan Williams wrote:
> On Tue, Jun 9, 2015 at 4:10 PM, Toshi Kani <toshi.kani@hp.com> wrote:
> > 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>
> >
> > 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 v5 patch series of
> > "libnvdimm: non-volatile memory devices".
> >
> > ---
> > 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
>
> Looks good to me. Once Rafael acks the ACPI core changes I'll pull it
> in to libnvdimm-for-next.
Great! Thanks Dan,
-Toshi
next prev parent reply other threads:[~2015-06-11 15:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 23:10 [PATCH v2 0/3] Add NUMA support for NVDIMM devices Toshi Kani
2015-06-09 23:10 ` [PATCH v2 1/3] acpi: Add acpi_map_pxm_to_online_node() Toshi Kani
2015-06-19 0:42 ` Rafael J. Wysocki
2015-06-19 1:16 ` Toshi Kani
2015-06-09 23:10 ` [PATCH v2 2/3] libnvdimm: Set numa_node to NVDIMM devices Toshi Kani
2015-06-09 23:10 ` [PATCH v2 3/3] libnvdimm: Add sysfs " Toshi Kani
2015-06-10 15:54 ` [PATCH v2 0/3] Add NUMA support for " Jeff Moyer
2015-06-10 15:57 ` Dan Williams
2015-06-10 16:11 ` Jeff Moyer
2015-06-10 16:20 ` Elliott, Robert (Server Storage)
2015-06-10 16:37 ` Dan Williams
2015-06-10 16:20 ` Toshi Kani
2015-06-11 15:38 ` Dan Williams
2015-06-11 15:45 ` Toshi Kani [this message]
2015-06-18 20:24 ` Dan Williams
2015-06-19 0:43 ` Rafael J. Wysocki
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=1434037550.11808.10.camel@misato.fc.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@lists.01.org \
--cc=rafael.j.wysocki@intel.com \
--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