Hello, Linus. On Tue, Mar 06, 2018 at 10:30:29AM -0800, Linus Torvalds wrote: > - can we split this patch up, so that if somebody bisects a problem > to it, we'll see if it's cgroup or aio that triggers it?
Will do. > So I'd like to either just make the thing always just use > WORK_CPU_UNBOUND, or hear some kind of (handwaving ok) explanation for > why something else would ever make sense. If the action is > fundamentally delayed by RCU, why would it make a difference which CPU > it runs on? It was mostly for consistency with other interfaces. Let's drop queue_work_on() for now. If ever necessary, we can easily add it back later. Thanks. -- tejun
