[lkml]   [2001]   [Nov]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Google's mm problems with 2.4.13 and 4G of memory
On November 1, 2001 09:00 pm, Sven Heinicke wrote:
> I got a Dell powerEdge something with 4G of memory locking up pritty
> hard when Danial Phillips test program hits chunk 9:
> mlocking at 401bf000 of size 1048576
> mlock took 12.181794 seconds
> munlock'ed 5999e000
> munmap'ed 5999e000
> Loading data at 5999e000 for slot 1
> Load (/mnt/sdb/sven/chunk9) succeeded!
> mlocking slot 1, 5999e000
> mlocking at 5999e000 of size 1048576
> And nothing. It's a vanilla 2.4.13 kernel and Mandrake 8.0.
> If I run the program up to like chunk 3 and send an interrupt it
> doesn't free up the memory unless I umount the file system.

Not freeing up the memory until umount is not a bug, it's normal. The
(cache) memory is supposed to be freed up when it's needed for something more

The discussion right now is about whether the mm is supposed to be able to
handle more than 50% mlocked memory or whether that's a user bug.

(I think we should be able to mlock >90% of memory, but there isn't general
agreement on this. The question is not whether it's possible, but whether
there's a real need for applications to be able to do this.)

> Please suggest idea on how to fix it. I have this system to abuse for
> several days.

Please stay tuned.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:12    [W:0.162 / U:0.024 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site