Re:The “too small to fail” memory-allocation rule
by dezgeg on Friday January 23, 2015 @12:15PM
(#8935957)
malloc() and free() is what I meant by "standard memory allocation functions". I'd say program that is in the position to use madvise() effectively has implemented it's own heap allocator.
Also, MADV_DONTNEED is only usable in some specific situations, like caches. I don't see how it could be used to implement things like "on low memory, trigger garbage collection and trim the heap to the smallest possible with munmap()".
Re:The “too small to fail” memory-allocation rule
by jbert on Sunday January 25, 2015 @06:33AM
(#8942674)
You said: "In other words, it's just wouldn't be practically possible to create an application that uses standard memory allocation functions and reliably can free some memory back to the kernel."
So I thought you'd be interested to know that you can do just this with the standard functions mmap() and madvise().
No, it's not a replacement for malloc/free, but it does have value to some applications for some use cases.
It's also a flag in posix_madvise(), so the concept is reasonably portable.