lkml.org 
[lkml]   [2009]   [Jul]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [PATCH 3/3] add isolate pages vmstat
Date
> > reproduce way
> > -----------------------
> > % ./hackbench 140 process 1000
> > => OOM occur
> >
> > active_anon:146 inactive_anon:0 isolated_anon:49245
> > active_file:79 inactive_file:18 isolated_file:113
> > unevictable:0 dirty:0 writeback:0 unstable:0 buffer:39
> > free:370 slab_reclaimable:309 slab_unreclaimable:5492
> > mapped:53 shmem:15 pagetables:28140 bounce:0
> >
> > @@ -1164,6 +1170,9 @@ static unsigned long shrink_inactive_lis
> > spin_lock_irq(&zone->lru_lock);
> > }
> > }
> > + __mod_zone_page_state(zone, NR_ISOLATED_ANON, -nr_anon);
> > + __mod_zone_page_state(zone, NR_ISOLATED_FILE, -nr_file);
> > +
> > } while (nr_scanned < max_scan);
>
> This is a non-trivial amount of extra stuff. Do we really need it?

In general, Administrator really hate large amount unaccounted memory.
Recent msgctl11 discussion, We faced it isolate pages about 1/3 system
memory.
Ahtough Rik's patch is applied, vmscan can isolate >1GB memory.

That's my point.







\
 
 \ /
  Last update: 2009-07-16 06:37    [W:0.114 / U:0.764 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site