2017-12-19 17:03 UTC+01:00, Christopher Lameter <c...@linux.com>: > On Tue, 19 Dec 2017, Frederic Weisbecker wrote: > >> Adding the boot parameter "isolcpus=nohz_offload" will now outsource >> these scheduler ticks to the global workqueue so that a housekeeping CPU >> handles that tick remotely. > > The vmstat processing required per cpu area access. How does that work if > the code is running on a remote processor?
It seems that current::sched_class::task_tick() is ok with this, as it uses per runqueues or per task datas. And both are passed as arguments.
