On Wed, Oct 10, 2018 at 04:07:42PM -0700, Alexander Duyck wrote: > This patch provides a new function queue_work_node which is meant to > schedule work on a "random" CPU of 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. > > For now we just default to the first CPU that is in the intersection of the > cpumask of the node and the online cpumask. The only exception is if the > CPU is local to the node we will just use the current CPU. This should work > for our purposes as we are currently only using this for unbound work so > the CPU will be translated to a node anyway instead of being directly used. > > As we are only using the first CPU to represent the NUMA node for now I am > limiting the scope of the function so that it can only be used with unbound > workqueues. > > Signed-off-by: Alexander Duyck <[email protected]>
Acked-by: Tejun Heo <[email protected]> Please let me know how you wanna route the patch. Thanks. -- tejun
