| |||||||||||||
KS2007: Memory management & application notification of low memoryKS2007: Memory management & application notification of low memoryPosted Sep 10, 2007 22:53 UTC (Mon) by vomlehn (subscriber, #45588)Parent article: KS2007: Memory management
The claim is that application developers will tend to avoid application notification of low memory conditions as it would be a Linux-specific extension. This is only an issue in situations where an application is targeted to multiple operating systems. In the embedded world, user-mode software tends to be more closely tied to the operating system. In addition, many embedded applications need the benefit of keeping around cached data as their network connections tend to be slower. As a result, I've already been toying with the notion of designing a framework for user mode software to return memory to the kernel on demand. I doubt I'm alone in this...and I certainly don't want to support it all myself...
(Log in to post comments)
KS2007: Memory management & application notification of low memory Posted Sep 13, 2007 22:07 UTC (Thu) by oak (subscriber, #2786) [Link] I think in Nokia internet tablets there's a notification about low memorysituations to applications through system D-BUS broadcasts[1]. Delivering information with D-BUS messages has obviously a latency issue if application is gobbling memory very fast, but I guess it works acceptably.
[1]
Btw. I think for applications which keep large freeable memory caches i.e.
KS2007: Memory management & application notification of low memory Posted Sep 13, 2007 22:30 UTC (Thu) by nix (subscriber, #2304) [Link] The glibc mmap threshold *minimum* is 128Kb. In recent versions of glibcthe threshold is dynamically adjusted between 128Kb and 512Kb (on 32-bit boxes) and 64Mb (on 64-bit). (The mmap threshold starts at 128Kb and rises whenever the application frees mmap()ed memory, so that transient allocations tend to use brk() instead.)
(This is new behaviour in glibc 2.5.)
KS2007: Memory management & application notification of low memory Posted Sep 16, 2007 19:43 UTC (Sun) by oak (subscriber, #2786) [Link] > The glibc mmap threshold *minimum* is 128Kb. In recent versions of glibcthe threshold is dynamically adjusted [...] (This is new behaviour in glibc 2.5.)
Can you still limit that to be smaller with MALLOC_MMAP_THRESHOLD_
However, in some environments and with some applications, the memory
KS2007: Memory management & application notification of low memory Posted Sep 16, 2007 23:11 UTC (Sun) by nix (subscriber, #2304) [Link] MALLOC_MMAP_THRESHOLD_ still works: it's precisely equivalent to callingmallopt (M_MMAP_THRESHOLD, ...); setting any of these mmap parameters disables dynamic adjustment completely.
KS2007: Memory management & application notification of low memory Posted Sep 20, 2007 11:20 UTC (Thu) by renox (subscriber, #23785) [Link] >>The claim is that application developers will tend to avoid application notification of low memory conditions as it would be a Linux-specific extension.<<
Note that a low memory condition doesn't have to be handled by the application developer to be useful:
|
|||||||||||||