lkml.org 
[lkml]   [2003]   [Feb]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: oom killer and its superior braindamage in 2.4


> On Sun, 23 Feb 2003, David Mansfield wrote:
>
> > Rik, any ideas?
>
> You could try the patch I sent to Marc and linux-kernel
> yesterday afternoon ;)
>

You miss my point completely. The kernel has ALREADY chosen a task to
kill. I don't care to adjust the 'badness' function. The kernel has
already chosen a bad task.

If you read my post, the bug is that the kernel CANNOT kill that process?
Why? If it's really a bad process, shouldn't it be the one that gets
killed?

With you patch we have:

1) Kernel goes OOM
2) Kernel picks the worst task to kill using badness()
3) Kernel attempts to kill this task but fails due to some {reason|bug}.
4) Kernel now picks some other task to kill even though the 'baddest' one
is allowed to hang out.

This is my question, and I don't see how the patch addresses it.

David



--
/==============================\
| David Mansfield |
| lkml@dm.cobite.com |
\==============================/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:33    [W:0.047 / U:8.904 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site