Re: writepage return value check in vmscan.c

[chrisl@vmware.com]

On Fri, Oct 25, 2002 at 11:44:14AM -0700, Andrew Morton wrote:
> chrisl@vmware.com wrote:
> > 
> > bigmm -i 3 -t 2 -c 1024
> 
> That's a nice little box killer you have there.

Thanks. It kills on all our customer's kernel, they don't use the
bleeding edge kernel at all. It is interesting to see vmware
serve as some heavy load stress test tool. It will give some real
world load to the OS, e.g. the load need to boot a windows etc. You
can stack many of them to abuse the OS.

> 
> With mem=4G, running bigmm -i 5 -t 2 -c 1024:
> 
> 2.4.19: Ran for a few minutes, got slower and slower and
> eventually stopped.  kupdate had taken 30 seconds CPU and
> all CPUs were spinning in shrink_cache().  Had to reset.
> 
> 2.4.20-pre8-ac1: Ran for a minute, froze up for a couple of
> minutes then recovered and remained comfortable.

How many instance of bigmm left there? It should be 10 bigmm
processes before oom kickin.

> 
> 2.5.44-mm5: had a few 0.5-second stalls in vmstat output, no
> other problems.
> 
> It's probably the list search failure, but I can't say for sure
> at this time.

Chris