about summary refs log tree commit diff
path: root/socket
diff options
context:
space:
mode:
authorSiddhesh Poyarekar <siddhesh@redhat.com>2012-09-25 14:10:29 +0530
committerSiddhesh Poyarekar <siddhesh@redhat.com>2012-09-25 14:30:52 +0530
commit9fab36eb583c0e585e83a01253299afed9ea9a11 (patch)
tree948ce03e0a724c8a3a7bca0fc1dbb7655f94e64e /socket
parent2b4f00d1a42b705521ca205ad8285dde82d84f2b (diff)
downloadglibc-9fab36eb583c0e585e83a01253299afed9ea9a11.tar.gz
glibc-9fab36eb583c0e585e83a01253299afed9ea9a11.tar.xz
glibc-9fab36eb583c0e585e83a01253299afed9ea9a11.zip
Shrink heap on linux when overcommit_memory == 2
Using madvise with MADV_DONTNEED to release memory back to the kernel
is not sufficient to change the commit charge accounted against the
process on Linux.  It is OK however, when overcommit is enabled or is
heuristic.  However, when overcommit is restricted to a percentage of
memory setting the contents of /proc/sys/vm/overcommit_memory as 2, it
makes a difference since memory requests will fail.  Hence, we do what
we do with secure exec binaries, which is to call mmap on the region
to be dropped with MAP_FIXED. This internally unmaps the pages in
question and reduces the amount of memory accounted against the
process.
Diffstat (limited to 'socket')
0 files changed, 0 insertions, 0 deletions