[lkml]   [2001]   [Nov]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Google's mm problem - not reproduced on 2.4.13
On November 2, 2001 07:48 pm, Sven Heinicke wrote:
> > Not freeing the memory is expected and normal. The previously-mlocked file
> > data remains cached in that memory, and even though it's not free, it's
> > 'easily freeable' so there's no smoking gun there. The reason the memory is
> > freed on umount is, there's no possibility that that file data can be
> > referenced again and it makes sense to free it up immediately.
> That cool and all, but how to I free up the memory w/o umounting the
> partition?

You don't, that's the mm's job. It tries to do it at the last minute, when
it's sure the memory is needed for something more important.

> Also, I just tried 2.4.14-pre7. It acted the same way as 2.4.13 does,
> requiring the reset key to continue.

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.039 / U:0.284 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site