Messages in this thread |  | | From | Sven Heinicke <> | Date | Fri, 2 Nov 2001 13:48:50 -0500 (EST) | Subject | Re: Google's mm problem - not reproduced on 2.4.13 |
| |
> 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 - 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/
|  |