[lkml]   [2000]   [Aug]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Out of memory?
David Ford wrote:

> The kernel does try to kill off programs when it runs out of memory but
> unless it picks the memory pig, then that program will probably immediately
> grab any memory the kernel just freed.

Killing, for instance, kswapd. On my machine last week, the kernel
started killing processes. Its first choice was kswapd, and then it went
on to my window manager and about 10 other programs.

It was pretty retarded.

I know Linux overcommits memory and has no way of knowing who the real
overallocator culprit is, but wouldn't some resource accounting be good?
Or perhaps a tunable or compile-time option to turn off overcommits?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:37    [W:0.074 / U:6.872 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site