Re: oom killer in 2.4.23

[Andrea Arcangeli]

On Thu, Dec 04, 2003 at 06:20:16PM +0100, Guillermo Menguez Alvarez wrote:
> > Yes, and as a side question, couldn't oom killer be made into a config
> > option?
> 
> As I see in the ChangeLog:
> 
> aa VM merge: page reclaiming logic changes: Kills oom killer
> 
> OOM Killer has been removed due to AA VM changes, so maybe it can't be
> cleanly enabled again.

it can be re-enabled without too much pain if you can accept the desktop
behaviour of 2.4.22 and previous not suitable for servers.

the oom killer had deadlocks and it was relaying on very inaccurate
accounting, so it had a number of corner cases were it was killing tasks
by mistakes (it's fooled by shm/mlock/noswap etc..), read also the bugreports
for 2.4.22 with tasks being killed because there was no swap in the box
(or just try to run your machine w/o swap, swap is not a must, it's a
wish).  Fixing those in 2.4 sounds too complicated, and now it's too
late to even hope to make a proper oom killer for 2.4.

For the record 2.2 was capable of checking iopl to defer a few times the
killing of the X server, that wasn't forward ported to 2.4. For 2.6 we
can do something better than all the past oom killers at least. 2.6 gets
fooled by mlock too btw, ranom kill tasks etc.. so it's not much better
than 2.4.22 was in oom killing respect.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/