Messages in this thread | | | Date | Mon, 22 May 2017 18:13:41 -0300 | From | Marcelo Tosatti <> | Subject | Re: [patch 2/2] MM: allow per-cpu vmstat_threshold and vmstat_worker configuration |
| |
On Mon, May 22, 2017 at 11:38:02AM -0500, Christoph Lameter wrote: > On Sat, 20 May 2017, Marcelo Tosatti wrote: > > > > And you can configure the interval of vmstat updates freely.... Set > > > the vmstat_interval to 60 seconds instead of 2 for a try? Is that rare > > > enough? > > > > Not rare enough. Never is rare enough. > > Ok what about the other stuff that must be going on if you allow OS > activity like f.e. the tick, scheduler etc etc.
Yes these are also problems... but we're either getting rid of them or reducing their impact as much as possible.
vmstat_update is one member of the problematic set.
I'll get you the detailed IPI measures, hold on...
| |