| |||||||||||||
Requesting 'real' memoryRequesting 'real' memoryPosted Feb 1, 2008 19:34 UTC (Fri) by giraffedata (subscriber, #1954)In reply to: Requesting 'real' memory by zlynx Parent article: Avoiding the OOM killer with mem_notify
Desktop applications aren't where I would expect to see deterministic memory allocation exploited. Allocation failures and crashes aren't such a big deal with these applications because if things fall apart, there's a user there to pick up the pieces. Overallocation and OOM Killer may well be the optimum memory management scheme for desktop systems. Where it matters is business-critical automated servers. For those, application writers do spend time considering running out of memory -- at least they do in cases where an OOM killer doesn't make it all pointless anyway. They check the success of getting memory and do it at a time when there is some reasonable way to respond to not getting it. And they shouldn't spend time worrying about freeing up swap space for other processes (i.e. mem_notify is no good). That resource management task belongs to the kernel and system administrator.
(Log in to post comments)
|
|||||||||||||