On Tue, 19 Dec 2017, Frederic Weisbecker wrote: > > 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.
So I guess no vmstat processing is required? vmstat does not use per task data but per cpu data.