On Wed, Oct 14, 2015 at 10:57 AM, Christoph Lameter <c...@linux.com> wrote: > > Well yes the schedule_delayed_work_on() call is from another cpu and the > schedule_delayed_work() from the same. No confusion there.
So "schedule_delayed_work()" does *not* guarantee that the work will run on the same CPU. Yes, yes, it so _happens_ that "add_timer()" preferentially uses the current CPU etc, so in practice it may have happened to work. But there's absolutely zero reason to think it should always work that way. If you want the scheduled work to happen on a particular CPU, then you should use "schedule_delayed_work_on()" It shouldn't matter which CPU you call it from. At least that's how I think the rules should be. Very simple, very clear: if you require a specific CPU, say so. Don't silently depend on "in practice, lots of times we tend to use the local cpu". Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/