Re: [RFC] Enabling other oom schemes

[Tvrtko A. UrÅulin]

Hello Rusty,

> I went ahead and added a new oom handler that is a combination of
> the original oom_kill.c combined with the changes from Tvrtko's patch
> (originally written for 2.4.20) that kills off parents that keep producing
> bad children.  It sounds a little right wing, but it works :->

Wow, great! I will try this as soon as I setup one extra machine for 2.6.0 
testing.

Regarding "right wing", well... you could say that. But it was usefull for one 
situation where one version of mysql (don't remeber which) used to go crazy. 
It was creating many childs what caused to load to go 250+ . Just to log in 
to that machine with ssh took more than 15minutes, and what then? Restart 
mysql. And the idea for this kind of oom killer was born. :) In more abstract 
words; we had a situation where user space app was causing server downtime 
(in a way). We have corrected it with an oom killer algorithm which reduces 
that downtime. 

I even posted it to LKML some time ago but received no comments.

I think that users should have choices, that is why your approach is so nice. 
Following those same lines, I don't understand why we should remove those 
choices from them/ourselves (like removing oom killer from 2.4 - why not make 
it a kconfig option instead?).

I really hope your modular approach gets into Linus tree!

Best regards,
Tvrtko A. Ursulin

-
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/