One person pointed out (rightly so) that this patch might end up killing a
Oracle process for example since it occupies more than 60% memory - which is
not good. While that may be case for a server, I think for a desktop this patch
is right - it allows the user to gain control on the machine whi
Parag Warudkar wrote:
oom_kill.c misses very obvious targets - For example, a process occupying >
80% memory, not superuser and not having hardware access gets ignored by it.
Logically, such a process, if killed , is going to make things return to
normal thereby eliminating the need for oom kill
oom_kill.c misses very obvious targets - For example, a process occupying >
80% memory, not superuser and not having hardware access gets ignored by it.
Logically, such a process, if killed , is going to make things return to
normal thereby eliminating the need for oom killer to further scan fo
3 matches
Mail list logo
