Messages in this thread |  | | From | Daniel Phillips <> | Subject | Re: Google's mm problem - not reproduced on 2.4.13 | Date | Sat, 3 Nov 2001 00:15:02 +0100 |
| |
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
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |