linux-kernel - Re: [RFC workqueue/driver-core PATCH 5/5] nvdimm: Schedule device registration on node local to the device

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 28 Sep 2018 10:46:20 -0700
From:   Dan Williams <dan.j.williams@...el.com>
To:     alexander.h.duyck@...ux.intel.com
Cc:     linux-nvdimm <linux-nvdimm@...ts.01.org>,
        Greg KH <gregkh@...uxfoundation.org>,
        Linux-pm mailing list <linux-pm@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Tejun Heo <tj@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        "Brown, Len" <len.brown@...el.com>,
        Dave Jiang <dave.jiang@...el.com>,
        "Rafael J. Wysocki" <rafael@...nel.org>,
        Vishal L Verma <vishal.l.verma@...el.com>,
        jiangshanlai@...il.com, Pavel Machek <pavel@....cz>,
        zwisler@...nel.org
Subject: Re: [RFC workqueue/driver-core PATCH 5/5] nvdimm: Schedule device
 registration on node local to the device

On Wed, Sep 26, 2018 at 2:52 PM Alexander Duyck
<alexander.h.duyck@...ux.intel.com> wrote:
>
> This patch is meant to force the device registration for nvdimm devices to
> be closer to the actual device. This is achieved by using either the NUMA
> node ID of the region, or of the parent. By doing this we can have
> everything above the region based on the region, and everything below the
> region based on the nvdimm bus.
>
> By guaranteeing NUMA locality I see an improvement of as high as 25% for
> per-node init of a system with 12TB of persistent memory.
>
> Signed-off-by: Alexander Duyck <alexander.h.duyck@...ux.intel.com>

Looks good to me. This does have a dependency on the current contents
of libnvdimm development tree.