#define PTRS 0x10
#define SIZE 0x1000
and do an strace of the code, it gives no memory back. I never said it
never gives memory back. Obviously, the malloc cache is a well tuned
low/high watermark mechanizm, and might not have a big effect, but it was
just an example. Probably X's (and Mozilla's) caches are much more serious
in size, but handling the destruction of them seems to be very nontrivial,
since their content has to be recreated by the application. (the malloc()
case special since the kernel can reconstruct page contents by zeroing
them out)
-- mingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/