[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180926215307.GA270328@devbig004.ftw2.facebook.com>
Date: Wed, 26 Sep 2018 14:53:07 -0700
From: Tejun Heo <tj@...nel.org>
To: Alexander Duyck <alexander.h.duyck@...ux.intel.com>
Cc: linux-nvdimm@...ts.01.org, gregkh@...uxfoundation.org,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
akpm@...ux-foundation.org, len.brown@...el.com,
dave.jiang@...el.com, rafael@...nel.org, vishal.l.verma@...el.com,
jiangshanlai@...il.com, pavel@....cz, zwisler@...nel.org,
dan.j.williams@...el.com
Subject: Re: [RFC workqueue/driver-core PATCH 1/5] workqueue: Provide
queue_work_near to queue work near a given NUMA node
Hello,
On Wed, Sep 26, 2018 at 02:51:38PM -0700, Alexander Duyck wrote:
> This patch provides a new function queue_work_near which is meant to
> schedule work on the nearest unbound CPU to the requested NUMA node. The
> main motivation for this is to help assist asynchronous init to better
> improve boot times for devices that are local to a specific node.
>
> Signed-off-by: Alexander Duyck <alexander.h.duyck@...ux.intel.com>
Why not just use unbound workqueues, which are NUMA-affine by default?
Are there big enough advantages?
Thanks.
--
tejun
Powered by blists - more mailing lists