[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1541550393.196084.202.camel@acm.org>
Date: Tue, 06 Nov 2018 16:26:33 -0800
From: Bart Van Assche <bvanassche@....org>
To: Alexander Duyck <alexander.h.duyck@...ux.intel.com>,
linux-kernel@...r.kernel.org, gregkh@...uxfoundation.org
Cc: linux-nvdimm@...ts.01.org, tj@...nel.org,
akpm@...ux-foundation.org, linux-pm@...r.kernel.org,
jiangshanlai@...il.com, rafael@...nel.org, len.brown@...el.com,
pavel@....cz, zwisler@...nel.org, dan.j.williams@...el.com,
dave.jiang@...el.com
Subject: Re: [driver-core PATCH v5 9/9] libnvdimm: Schedule device
registration on node local to the device
On Mon, 2018-11-05 at 13:12 -0800, Alexander Duyck 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.
Thank you for having included the performance numbers.
Reviewed-by: Bart Van Assche <bvanassche@....org>
Powered by blists - more mailing lists