[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180926220957.GB270328@devbig004.ftw2.facebook.com>
Date: Wed, 26 Sep 2018 15:09:57 -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 03:05:17PM -0700, Alexander Duyck wrote:
> I am using unbound workqueues. However there isn't an interface that
> exposes the NUMA bits of them directly. All I am doing with this
> patch is adding "queue_work_near" which takes a NUMA node as an
> argument and then copies the logic of "queue_work_on" with the
> exception that I am doing a check to verify that there is an
> intersection between wq_unbound_cpumask and the cpumask of the node,
> and then passing a CPU from that intersection into "__queue_work".
Can it just take a cpu id and not feed that to __queue_work()? That
looks like a lot of extra logic.
Thanks.
--
tejun
Powered by blists - more mailing lists