Re: [PATCH] Remove OOM killer from try_to_free_pages / all_unreclaimable braindamage

Bodo Eggert
2004-11-18T23:41:33Z

Werner Almesberger wrote:

> A process could declare itself as usual suspect. This would then be
> recorded as a per-task flag, to be inherited by children. Now, one
> could write a launcher like this:

You'll have some precompiled binaries causing trouble, while other
precompiled binaries will be killed while you want them to stay alife.
Sometimes you'll have the same binary (e.g. perl or java) running a
"notme"-task like watching the log for intrusion while at the same time
processing a very large image.

The best solution I can think of is attaching a kill priority (similar to
the nice value). Before killing, this value would be added to lg_2(memsize),
and the least desirable process would "win", even if it's sshd running wild.

For the trashing problem: I like the idea of sending a signal to stop the
process, but it should rather be a request to stop that can be caught by
the process. A SETI-like task could save its workset and free the memory
instead, a browser would discard it's memory cache and pause loading
Images for the sites etc.
--
The newest and least experienced soldier will usually win the Congressional
Medal Of Honor.

Friß, Spammer: abuse@online-loanz.com cxePdomFs@suncoastrewards.com