From: Dan Williams <dan.j.williams@intel.com>
To: alexander.h.duyck@linux.intel.com
Cc: "Brown, Len" <len.brown@intel.com>,
Linux-pm mailing list <linux-pm@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
linux-nvdimm <linux-nvdimm@lists.01.org>,
jiangshanlai@gmail.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
zwisler@kernel.org, Pavel Machek <pavel@ucw.cz>,
Tejun Heo <tj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [RFC workqueue/driver-core PATCH 5/5] nvdimm: Schedule device registration on node local to the device
Date: Fri, 28 Sep 2018 10:46:20 -0700 [thread overview]
Message-ID: <CAPcyv4gK59QVke3a3Lt4Ds_yYTLiDFjte8DcPqaH1pZ4otFrAg@mail.gmail.com> (raw)
In-Reply-To: <20180926215201.13512.55945.stgit@localhost.localdomain>
On Wed, Sep 26, 2018 at 2:52 PM Alexander Duyck
<alexander.h.duyck@linux.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@linux.intel.com>
Looks good to me. This does have a dependency on the current contents
of libnvdimm development tree.
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: Dan Williams <dan.j.williams@intel.com>
To: alexander.h.duyck@linux.intel.com
Cc: linux-nvdimm <linux-nvdimm@lists.01.org>,
Greg KH <gregkh@linuxfoundation.org>,
Linux-pm mailing list <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Tejun Heo <tj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Brown, Len" <len.brown@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Vishal L Verma <vishal.l.verma@intel.com>,
jiangshanlai@gmail.com, Pavel Machek <pavel@ucw.cz>,
zwisler@kernel.org
Subject: Re: [RFC workqueue/driver-core PATCH 5/5] nvdimm: Schedule device registration on node local to the device
Date: Fri, 28 Sep 2018 10:46:20 -0700 [thread overview]
Message-ID: <CAPcyv4gK59QVke3a3Lt4Ds_yYTLiDFjte8DcPqaH1pZ4otFrAg@mail.gmail.com> (raw)
In-Reply-To: <20180926215201.13512.55945.stgit@localhost.localdomain>
On Wed, Sep 26, 2018 at 2:52 PM Alexander Duyck
<alexander.h.duyck@linux.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@linux.intel.com>
Looks good to me. This does have a dependency on the current contents
of libnvdimm development tree.
next prev parent reply other threads:[~2018-09-28 17:46 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 21:51 [RFC workqueue/driver-core PATCH 0/5] Add NUMA aware async_schedule calls Alexander Duyck
2018-09-26 21:51 ` Alexander Duyck
2018-09-26 21:51 ` Alexander Duyck
2018-09-26 21:51 ` [RFC workqueue/driver-core PATCH 1/5] workqueue: Provide queue_work_near to queue work near a given NUMA node Alexander Duyck
2018-09-26 21:51 ` Alexander Duyck
2018-09-26 21:51 ` Alexander Duyck
2018-09-26 21:53 ` Tejun Heo
2018-09-26 21:53 ` Tejun Heo
2018-09-26 21:53 ` Tejun Heo
2018-09-26 22:05 ` Alexander Duyck
2018-09-26 22:05 ` Alexander Duyck
2018-09-26 22:09 ` Tejun Heo
2018-09-26 22:09 ` Tejun Heo
2018-09-26 22:09 ` Tejun Heo
2018-09-26 22:19 ` Alexander Duyck
2018-09-26 22:19 ` Alexander Duyck
2018-10-01 16:01 ` Tejun Heo
2018-10-01 16:01 ` Tejun Heo
2018-10-01 16:01 ` Tejun Heo
2018-10-01 21:54 ` Alexander Duyck
2018-10-01 21:54 ` Alexander Duyck
2018-10-01 21:54 ` Alexander Duyck
2018-10-02 17:41 ` Tejun Heo
2018-10-02 17:41 ` Tejun Heo
2018-10-02 17:41 ` Tejun Heo
2018-10-02 18:23 ` Alexander Duyck
2018-10-02 18:23 ` Alexander Duyck
2018-10-02 18:23 ` Alexander Duyck
2018-10-02 18:41 ` Tejun Heo
2018-10-02 18:41 ` Tejun Heo
2018-10-02 18:41 ` Tejun Heo
2018-10-02 20:49 ` Alexander Duyck
2018-10-02 20:49 ` Alexander Duyck
2018-10-02 20:49 ` Alexander Duyck
2018-09-26 21:51 ` [RFC workqueue/driver-core PATCH 2/5] async: Add support for queueing on specific " Alexander Duyck
2018-09-26 21:51 ` Alexander Duyck
2018-09-27 0:31 ` Dan Williams
2018-09-27 0:31 ` Dan Williams
2018-09-27 0:31 ` Dan Williams
2018-09-27 15:16 ` Alexander Duyck
2018-09-27 15:16 ` Alexander Duyck
2018-09-27 15:16 ` Alexander Duyck
2018-09-27 19:48 ` Dan Williams
2018-09-27 19:48 ` Dan Williams
2018-09-27 20:03 ` Alexander Duyck
2018-09-27 20:03 ` Alexander Duyck
2018-09-26 21:51 ` [RFC workqueue/driver-core PATCH 3/5] driver core: Probe devices asynchronously instead of the driver Alexander Duyck
2018-09-26 21:51 ` Alexander Duyck
2018-09-26 21:51 ` Alexander Duyck
2018-09-27 0:48 ` Dan Williams
2018-09-27 0:48 ` Dan Williams
2018-09-27 0:48 ` Dan Williams
2018-09-27 15:27 ` Alexander Duyck
2018-09-27 15:27 ` Alexander Duyck
2018-09-27 15:27 ` Alexander Duyck
2018-09-28 2:48 ` Dan Williams
2018-09-28 2:48 ` Dan Williams
2018-09-28 2:48 ` Dan Williams
2018-09-26 21:51 ` [RFC workqueue/driver-core PATCH 4/5] driver core: Use new async_schedule_dev command Alexander Duyck
2018-09-26 21:51 ` Alexander Duyck
2018-09-26 21:51 ` Alexander Duyck
2018-09-28 17:42 ` Dan Williams
2018-09-28 17:42 ` Dan Williams
2018-09-28 17:42 ` Dan Williams
2018-09-26 21:52 ` [RFC workqueue/driver-core PATCH 5/5] nvdimm: Schedule device registration on node local to the device Alexander Duyck
2018-09-26 21:52 ` Alexander Duyck
2018-09-26 21:52 ` Alexander Duyck
2018-09-28 17:46 ` Dan Williams [this message]
2018-09-28 17:46 ` 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=CAPcyv4gK59QVke3a3Lt4Ds_yYTLiDFjte8DcPqaH1pZ4otFrAg@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.h.duyck@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jiangshanlai@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=tj@kernel.org \
--cc=zwisler@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.