summaryrefslogtreecommitdiffstats
path: root/fs
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2015-10-15 22:01:50 +0200
committerLinus Torvalds <torvalds@linux-foundation.org>2015-10-15 22:01:50 +0200
commit176bed1de5bf977938cad26551969eca8f0883b1 (patch)
tree45adb32e0c98e146ada11f1db777dfd0eced1bbc /fs
parentMerge branch 'for-4.3-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git... (diff)
downloadlinux-176bed1de5bf977938cad26551969eca8f0883b1.tar.xz
linux-176bed1de5bf977938cad26551969eca8f0883b1.zip
vmstat: explicitly schedule per-cpu work on the CPU we need it to run on
The vmstat code uses "schedule_delayed_work_on()" to do the initial startup of the delayed work on the right CPU, but then once it was started it would use the non-cpu-specific "schedule_delayed_work()" to re-schedule it on that CPU. That just happened to schedule it on the same CPU historically (well, in almost all situations), but the code _requires_ this work to be per-cpu, and should say so explicitly rather than depend on the non-cpu-specific scheduling to schedule on the current CPU. The timer code is being changed to not be as single-minded in always running things on the calling CPU. See also commit 874bbfe600a6 ("workqueue: make sure delayed work run in local cpu") that for now maintains the local CPU guarantees just in case there are other broken users that depended on the accidental behavior. Cc: Christoph Lameter <cl@linux.com> Cc: Tejun Heo <tj@kernel.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions