Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1585171
| From | Michal Hocko <mhocko@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH V2 5/7] mm: add vmstat account for MADV_FREE pages |
| Date | 2017-02-21 10:50 +0100 |
| Message-ID | <tdff5-Kd-25@gated-at.bofh.it> (permalink) |
| References | <t6VCp-c7-3@gated-at.bofh.it> <t6VCq-c7-17@gated-at.bofh.it> <t9jqV-3TZ-3@gated-at.bofh.it> <tdff5-Kd-27@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Sorry for a late reply I was on vacation last week] On Fri 10-02-17 09:50:15, Shaohua Li wrote: > On Fri, Feb 10, 2017 at 02:27:27PM +0100, Michal Hocko wrote: > > On Fri 03-02-17 15:33:21, Shaohua Li wrote: > > > Show MADV_FREE pages info in proc/sysfs files. > > > > How are we going to use this information? Why it isn't sufficient to > > watch for lazyfree events? I mean this adds quite some code and it is > > not clear (at least from the changelog) we we need this information. > > It's just like any other meminfo we added to let user know what happens in the > system. Users can use the info for monitoring/diagnosing. the > lazyfree/lazyfreed events can't reflect the lazyfree page info because > 'lazyfree - lazyfreed' doesn't equal current lazyfree pages and the events > aren't per-node. I'll add more description in the changelog. Well, I would prefer to not add new counters until there is a strong reason for them. Maybe a trace point would be more appropriate for debugging purposes. -- Michal Hocko SUSE Labs
Back to linux.kernel | Previous | Next | Find similar | Unroll thread
Re: [PATCH V2 5/7] mm: add vmstat account for MADV_FREE pages Michal Hocko <mhocko@kernel.org> - 2017-02-21 10:50 +0100
csiph-web