Re: VM nuisance

[Maciej Zenczykowski]

> No.  The problem is that whenever I change something to
> the OOM killer I get flamed.
>
> Both by the people for whom the OOM killer kicks in too
> early and by the people for whom the OOM killer now doesn't
> kick in.
>
> I haven't got the faintest idea how to come up with an OOM
> killer which does the right thing for everybody.

How about adding some sort of per-process priority (i.e. a la nice) which
would determine the order in which they would be OOMed? Then we could
safely run X with a kigh KillMe and Netscape with an even higher KillMe
and we would probably avoid the something useing too much memory let's
kill root's shell...

[i.e. if a lower KillMe proc runs out of memory we kill off the process
with the highest KillMe using most mem and can safely give this mem to the
proc which just ran out]

MaZe.