Re: Google's mm problem - not reproduced on 2.4.13

Daniel Phillips
2001-11-02T23:14:15Z

On November 2, 2001 11:42 pm, Ben Smith wrote:
> As another note, I've re-written my test application to use madvise
> instead of mlock, on a suggestion from Andrea. It also doesn't work. For
> 2.4.13, after running for a while, my test app hangs, using one CPU, and
> kswapd consumes the other CPU. I was eventually able to kill my test app.

OK, while there may be room for debate over whether the mlock problem is a
bug there's no question with madvise. The program still doesn't work if you
replace the mlocks with madvises (except for the mlock that's used to
estimate memory size).

--
Daniel