[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <x49zj47v8zi.fsf@segfault.boston.devel.redhat.com>
Date: Wed, 10 Jun 2015 12:11:45 -0400
From: Jeff Moyer <jmoyer@...hat.com>
To: Dan Williams <dan.j.williams@...el.com>
Cc: Toshi Kani <toshi.kani@...com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Linux ACPI <linux-acpi@...r.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
linux-nvdimm <linux-nvdimm@...1.01.org>
Subject: Re: [PATCH v2 0/3] Add NUMA support for NVDIMM devices
Dan Williams <dan.j.williams@...el.com> writes:
> On Wed, Jun 10, 2015 at 8:54 AM, Jeff Moyer <jmoyer@...hat.com> wrote:
>> 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?
>>
>
> 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-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