[Bug libc/167] malloc() eats excess ram

[bluefoxicy at linux dot net]

------- Additional Comments From bluefoxicy at linux dot net  2004-06-20 20:17 -------
Petter:
  I appreciate your actual reply, but try reading.

I am not suggesting using mmap() for each allocation; I am suggesting using
mmap() to build a virtual segment of memory to use in place of the heap which
may allow more complex operations which return free memory to the system, reduce
the impact of fragmentation, and possibly even to increase the speed of
allocations and especially realloc(), to be implemented.  The changes in the
allocator should be transparent to the application.

Try reading the blog, all of the text I've placed on both bugzillas, and the
message to libc-alpha.  Especially read comment 4 on this bugzilla:

    This would be a crossbreed between what I understand
    to be the current heap-based malloc() code in glibc/
    malloc and the current mmap() fallback in glibc/malloc,
    right?  It might work excessively well.

-- 


http://sources.redhat.com/bugzilla/show_bug.cgi?id=167

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.