OOM stupidity
When the OOM kills the process that I am currently composing within (an active character stream), that is a MICROSOFT WINDOWS behavior. I don't care if it's hogging the machine, *I'M* using it! That is the point after all, isn't it? A human sysadmin could kill my process (and then I would have dealings with him), but the logic here is badly flawed.
If this is what Linux will become in the 2.4 kernel, *FORGET IT*. Swap was hardly filled up, and remember it's the 2xRAM swap size now! Has Linux been too eager to accept recent windows converts (and prior to their recovery from that brain damage) and lost it's sharp edge of careful thought and tooling that was it's hallmark in the beginning?? Are the maintainers of this area too busy "protecting their turf" to allow some options to the end user? Seem like Linus better kick some butt before it's too late. Microsoft has been running a disinformation campaign against Linux for awhile, but the current OOM behavior could allow them to make a major capitalization against Linux.
Just think of the Microsoft campaign :
"We don't pull the rug out from underneath you".
(Note to all those that will jump up and claim that Microsoft has problems -- I see, you are saying because MS is faulty, it's OK that Linux is faulty)
Where is a patch to allow the sensible OOM I had in prior kernels? (cause this crap is getting pitched)
--------
(kernel 2.4.4-pre6, not noticed in eariler kernels, but machine was not that heavily used. Hardware has been rock solid for years. Load at the time was trivial compared to 2.0 series kernels workload.)
____
ron
- I don't need no stinkin multiline sig -
Quoted 2 lines
Where is a patch to allow the sensible OOM I had in prior kernels? (cause this crap is getting pitched)
I gave Alan a patch to fix the problem where the OOM activates too early (eg. when there's still plenty of swap and buffer memory to eat). I don't know whether this made it into the mainstream kernel, but from the sound of it, it didn't.
I also did some work on the OOM killer itself (so that it tries to be more intelligent about *what* it kills), and I'm fairly certain that didn't get accepted.
If you like, I can post a patch containing these two fixes.
--------------------------------------------------------------
from: Jonathan "Chromatix" Morton mail: [email protected] (not for attachments) big-mail: [email protected] uni-mail: [email protected]
The key to knowledge is not to rely on people to teach you it.
Get VNC Server for Macintosh from http://www.chromatix.uklinux.net/vnc/
-----BEGIN GEEK CODE BLOCK-----
Version 3.12
GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*) -----END GEEK CODE BLOCK-----
Quoted 3 lines
Swap was hardly filled up, and remember it's the 2xRAM swap size now! Has Linux been too eager to accept recent windows converts (and prior to their recovery from that brain damage) and lost it's sharp edge of
The Linux tree OOM trigger is way wrong right now. We know
Quoted 2 lines
Where is a patch to allow the sensible OOM I had in prior kernels? (cause this crap is getting pitched)
Try -ac (or 2.2.19 for now)