Messages in this thread | | | Date | Tue, 03 Apr 2007 22:56:59 -0400 | From | Rik van Riel <> | Subject | Re: missing madvise functionality |
| |
Marko Macek wrote: > Ulrich Drepper wrote: >> A solution for this problem is a madvise() operation with the following >> property: >> >> - the content of the address range can be discarded >> >> - if an access to a page in the range happens in the future it must >> succeed. The old page content can be provided or a new, empty page >> can be provided > > Doesn't this conflict with disabling overcommit?
Not really. The threshold below which glibc does not give memory back to the kernel at all is dynamic already. It is entirely possible to make an application that frees tens of thousands of 3000 byte chunks, in a pattern that makes it impossible for glibc to return any memory to the kernel.
If you want to run without overcommit, don't run too close to the wire :)
-- Politics is the struggle between those who want to make their country the best in the world, and those who believe it already is. Each group calls the other unpatriotic. - 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/
| |