From: Andrea Arcangeli <andrea@suse.de>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Daniel Stone <daniel@kabuki.eyep.net>, linux-kernel@vger.kernel.org
Subject: Re: Rik's bad process killer - how to kill _IT_?
Date: Wed, 22 Nov 2000 16:44:43 +0100 [thread overview]
Message-ID: <20001122164443.C6106@athlon.random> (raw)
In-Reply-To: <20001122123115Z129851-8303+80@vger.kernel.org> <Pine.LNX.4.21.0011221205320.12459-100000@duckman.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0011221205320.12459-100000@duckman.distro.conectiva>; from riel@conectiva.com.br on Wed, Nov 22, 2000 at 12:07:48PM -0200
On Wed, Nov 22, 2000 at 12:07:48PM -0200, Rik van Riel wrote:
> judging from your lack of error messages you're running
> 2.2 [..]
Recent 2.2.x:
if (error_code & 4)
{
if (tsk->oom_kill_try++ > 10 ||
!((regs->eflags >> 12) & 3))
{
printk("VM: killing process %s\n", tsk->comm);
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
do_exit(SIGKILL);
}
else
{
/*
* The task is running with privilegies and so we
* trust it and we give it a chance to die gracefully.
*/
printk("VM: terminating process %s\n", tsk->comm);
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
force_sig(SIGTERM, current);
if (tsk->oom_kill_try > 1)
{
tsk->policy |= SCHED_YIELD;
schedule();
}
return;
}
}
Older 2.2.x:
void oom(struct task_struct * task)
{
printk("\nOut of memory for %s.\n", task->comm);
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
force_sig(SIGKILL, task);
}
In short if he doesn't get any message from the kernel (and the machine doesn't
soft-lockup :) it's not an oom issue.
Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-22 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-22 12:02 Rik's bad process killer - how to kill _IT_? Daniel Stone
2000-11-22 14:07 ` Rik van Riel
2000-11-22 15:44 ` Andrea Arcangeli [this message]
2000-11-22 19:25 ` Daniel Stone
2000-11-22 17:05 ` Igmar Palsenberg
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=20001122164443.C6106@athlon.random \
--to=andrea@suse.de \
--cc=daniel@kabuki.eyep.net \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.