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

Sven Heinicke
2001-11-02T18:49:59Z

> 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?

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

Sven