Hello, On Mon, Feb 08, 2021 at 03:54:14PM -0500, Johannes Weiner wrote: > We probably do need a better solution for the lruvecs as well, but in > this case it just started holding up fixing the memory.stat issue for > no reason and so I tabled it for another patch series. rstat doesn't currently have a flush throttling mechanism cuz it doens't expect readers to be super hot but adding one should be pretty easy - e.g. it can just keep track of the number of updates on this cpu since the last flush and then flush iff the it's above a certain threshold. Shouldn't be too difficult to match or exceed the performance and error characteristics of the existing code. Thanks. -- tejun
