Messages in this thread | | | Date | Tue, 7 Jul 2009 21:51:26 +0800 | From | Wu Fengguang <> | Subject | Re: [PATCH 4/5] add isolate pages vmstat |
| |
On Tue, Jul 07, 2009 at 09:19:53AM +0800, KOSAKI Motohiro wrote: > > > > Index: b/mm/vmscan.c > > > > =================================================================== > > > > --- a/mm/vmscan.c > > > > +++ b/mm/vmscan.c > > > > @@ -1082,6 +1082,7 @@ static unsigned long shrink_inactive_lis > > > > -count[LRU_ACTIVE_ANON]); > > > > __mod_zone_page_state(zone, NR_INACTIVE_ANON, > > > > -count[LRU_INACTIVE_ANON]); > > > > + __mod_zone_page_state(zone, NR_ISOLATED_ANON + file, nr_taken); > > > > > > Lumpy can reclaim file + anon anywhere. > > > How about using count[NR_LRU_LISTS]? > > > > Ah yes, good catch. > > Fixed. > > Subject: [PATCH] add isolate pages vmstat > > If the system have plenty threads or processes, concurrent reclaim can > isolate very much pages. > Unfortunately, current /proc/meminfo and OOM log can't show it. > > This patch provide the way of showing this information.
Acked-by: Wu Fengguang <fengguang.wu@intel.com>
> printk("Active_anon:%lu active_file:%lu inactive_anon:%lu\n" > - " inactive_file:%lu" > - " unevictable:%lu" > + " inactive_file:%lu unevictable:%lu\n" > + " isolated_anon:%lu isolated_file:%lu\n"
How about active_anon inactive_anon isolated_anon active_file inactive_file isolated_file ?
Thanks, Fengguang
| |