From: David Mansfield <lkml@dm.cobite.com>
To: Rik van Riel <riel@imladris.surriel.com>
Cc: linux-kernel@vger.kernel.org,
Marc-Christian Petersen <m.c.p@wolk-project.de>
Subject: Re: oom killer and its superior braindamage in 2.4
Date: Sun, 23 Feb 2003 13:07:18 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0302231301400.23778-100000@admin> (raw)
In-Reply-To: <Pine.LNX.4.50L.0302231325230.2206-100000@imladris.surriel.com>
> 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 |
\==============================/
next prev parent reply other threads:[~2003-02-23 17:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-23 16:06 David Mansfield
2003-02-23 16:25 ` Faik Uygur
2003-02-23 16:25 ` Rik van Riel
2003-02-23 18:07 ` David Mansfield [this message]
2003-02-23 20:14 ` Rik van Riel
2003-02-23 20:22 ` David Mansfield
2003-02-23 20:53 ` Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2003-02-24 9:13 Mikael Starvik
2003-02-24 9:27 ` Marc-Christian Petersen
2003-02-22 19:35 Marc-Christian Petersen
2003-02-22 20:14 ` Rik van Riel
2003-02-22 20:32 ` Rik van Riel
2003-02-23 17:35 ` Marc-Christian Petersen
2003-02-23 20:18 ` Rik van Riel
2003-02-23 20:29 ` Marc-Christian Petersen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0302231301400.23778-100000@admin \
--to=lkml@dm.cobite.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.de \
--cc=riel@imladris.surriel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®