We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Implementation of GLIBC memory allocator malloc_trim functionality to address memory fragmentation of the SSM process
Implement and malloc_trim API call, part of GLIBC memory allocator API, provided by the GLIBC runtime, inside of the SSM.
The call invokes the linux kernel syscall sbrk and madvise which shrink the free top of the heap chunk allocated for small allocations and releases the memory pages back to the OS (kernel space) of unallocated chunks on the fastbin collection of unallocated memory chunks withing the GLIBC memory allocators memory arena.
The call is part of the GNU C extensions that are specific to the GLIBC implementation of user space memory allocator functionality and are part of the malloc.h/malloc.c code base and part of the C runtime shipped with any Linux distribution.
The call addresses the issue of fragmentation of memory and creeping memory allocation footprint, that is a side effect of (well documented and researched)GLIB C user space memory allocation algorithm and memory book-keeping mechanism and handling for allocations for small memory chunks.
The call should be invoked periodically within the SSM to clean up the un-used small allocations accumulated within the GLIBC memory allocator. The interval between the invocations (in seconds) should be configurable by an environment variable passed within the application profile. If the environment variable is not set, or the interval set to 0 the malloc_trim invocation should be disabled.
Do not place IBM confidential, company confidential, or personal information into any field.