On Thu, Nov 8, 2018 at 10:06 AM Alexander Duyck <[email protected]> wrote: > > Provide 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. > > Acked-by: Tejun Heo <[email protected]> > Reviewed-by: Bart Van Assche <[email protected]> > Signed-off-by: Alexander Duyck <[email protected]>
Acked-by: Dan Williams <[email protected]> _______________________________________________ Linux-nvdimm mailing list [email protected] https://lists.01.org/mailman/listinfo/linux-nvdimm
