Hello, Mel. On Mon, Jan 23, 2017 at 08:04:12PM +0000, Mel Gorman wrote: > What is the actual mechanism that does that? It's not something that > schedule_on_each_cpu does and one would expect that the core workqueue > implementation would get this sort of detail correct. Or is this a proposal > on how it should be done? If you use schedule_on_each_cpu(), it's all fine as the thing pins cpus and waits for all the work items synchronously. If you wanna do it asynchronously, right now, you'll have to manually synchronize work items against the offline callback manually. On this area, the current workqueue behavior is pretty bad. Historically, we didn't distinguish affinity-for-optimization affinity-for-correctness, so we couldn't really enforce strong behaviors on it. We started distinguishing them some releases ago, so I should revisit it soon. Thanks. -- tejun -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
