On Thu, May 11, 2017 at 10:37:07AM -0500, Christoph Lameter wrote: > On Tue, 2 May 2017, Luiz Capitulino wrote: > > > Ah, OK. Got this now. I'll give this patch a try. But I think we want > > to hear from Christoph (who worked on reducing the vmstat interruptions > > in the past). > > A bit confused by this one. The vmstat worker is already disabled if there > are no updates. Also the patches by Chris Metcalf on data plane mode add a > prctl to quiet the vmstat workers. > > Why do we need more than this? If there are vmstat statistic updates on a given CPU, and you don't want intervention from the vmstat worker, you change the behaviour of stat data collection to directly write to the global structures (which disables the performance optimization of collecting data in per-cpu counters). This way you can disable vmstat worker (because it causes undesired latencies), while allowing vmstatistics to function properly. The prctl from Chris Metcalf patchset allows one to disable vmstat worker per CPU? If so, they replace the functionality of the patch "[patch 3/3] MM: allow per-cpu vmstat_worker configuration" of the -v2 series of my patchset, and we can use it instead. Is it integrated already? -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
