Hello, On Tue, Feb 03, 2015 at 03:26:28AM +0000, Petr Cermak wrote: > On Mon, Jan 26, 2015 at 04:00:20PM -0800, David Rientjes wrote: > > [...] > > This is a result of allowing something external (process B) be able to > > clear hwm so that you never knew the value went to 100MB. That's the > > definition of a race, I don't know how to explain it any better and making > > any connection between clearing PG_referenced and mm->hiwater_rss is a > > stretch. This approach just makes mm->hiwater_rss meaningless. > > I understand your concern, but I hope you agree that the functionality we > are proposing would be very useful for profiling. Therefore, I suggest > adding an extra resettable field to /proc/pid/status (e.g. > resettable_hiwater_rss) instead. What is your view on this approach? The idea would be very useful for measuring working set size for efficient memory management in userside, which becomes very popular with many platforms for embedded world with tight memory. > > -- > 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> -- Kind regards, Minchan Kim -- 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>