Hi,
When a system runs out of memory (OOM), the Linux OOM killer
makes a best effort guess
at which program is being excessive about its memory usage.
Unfortunately it isn't always correct
especially on embedded systems.
I noticed that there was a person proposed an idea to replace
the default
kernel OOM with a module in CGL discussion, and he also gave out a patch
for 2.6.0-pre11,
which can be found at http://www.rossfell.co.uk/~rickp/oom/.
How about your idea on the proposal? Any comments are welcome!
Thanks
Guo Min
The content of this email message solely contains my own personal views,
and not those of my employer.
On Monday 01 March 2004 06:53, Guo, Min wrote:
> How about your idea on the proposal? Any comments are welcome!
You can also try:
http://www.linux.ursulin.net/moom-2.4.22-1.patch
Though it hasn't been updated for a while because nobody cares...
On Mon, 2004-03-01 at 12:41, Tvrtko A. Ur?ulin wrote:
> On Monday 01 March 2004 06:53, Guo, Min wrote:
>
> > How about your idea on the proposal? Any comments are welcome!
>
> You can also try:
>
> http://www.linux.ursulin.net/moom-2.4.22-1.patch
>
> Though it hasn't been updated for a while because nobody cares...
IMHO problem with OOM killer is that it always will do wrong choice. So,
it should be either plugin based or allow to configure it and this
means, that it will become more complex and buggy. Does not it mean,
that OOM killer should be moved to user space?
How about to export OOM event to user space? It might be done in manner
like hotplug script is used.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
umka
Hi!
> > Though it hasn't been updated for a while because nobody cares...
> IMHO problem with OOM killer is that it always will do wrong choice. So,
> it should be either plugin based or allow to configure it and this
> means, that it will become more complex and buggy. Does not it mean,
> that OOM killer should be moved to user space?
>
> How about to export OOM event to user space? It might be done in manner
> like hotplug script is used.
When you are OOM, you really can't exec userland script...
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
On Thursday 04 March 2004 13:29, Yury V. Umanets wrote:
> IMHO problem with OOM killer is that it always will do wrong choice. So,
> it should be either plugin based or allow to configure it and this
> means, that it will become more complex and buggy. Does not it mean,
> that OOM killer should be moved to user space?
>
> How about to export OOM event to user space? It might be done in manner
> like hotplug script is used.
No, I don't think userspace is a good idea.
On the other hand... I have updated the MOOM patch in sync with 2.4.25, you
can get it at http://linux.ursulin.net or from LKML.
Any comments, bug reports, etc are welcomed!
--
Best regards,
Tvrtko A. Ur?ulin, Linux admin
--
Croadria Internet usluge <http://www.croadria.com>
- Web hosting (Linux & Windows), E-commerce