From: Kristian Peters <kristian.peters@korseby.net>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org,
"Robert L. Harris" <Robert.L.Harris@rdlg.net>
Subject: Re: oom killer in 2.4.23
Date: Sat, 6 Dec 2003 10:31:43 +0100 [thread overview]
Message-ID: <20031206103143.027ba4ec.kristian.peters@korseby.net> (raw)
In-Reply-To: <20031205195800.GB2121@dualathlon.random>
Andrea Arcangeli <andrea@suse.de> schrieb:
> what you're complaining is the 'selection of the task to be killed'.
> That's not solvable. the kernel can't read your brain period. Only if
> the kernel could read the brain of the adminstrator then you would be
> happy, there is no way the kernel can know which is the task you really
> want to have killed first.
I agree. On a server the most likely application to be killed would be the service with the most pages in memory. And those services tend to be the important ones.
However, for a simple desktop-linux that statistical approach seems to be wrong. Your vm has even killed /sbin/getty sometimes, so that I can't login via a simple console.
Re-enabling the oom-killer gives a good result for me:
Dec 6 09:46:19 adlib kernel: Out of Memory: Killed process 643 (khexedit).
Dec 6 09:48:42 adlib kernel: Out of Memory: Killed process 645 (khexedit).
What I complain is that your vm kills some processes without mentioning in the logs. How can I determine what processes the kernel has killed ?
I hope that fairly simple patch does things right for all people that want the old behaviour. It's already a year ago I last hacked on the kernel.
diff -rauN linux-2.4.23/include/linux/sched.h linux-2.4.23-kp1/include/linux/sched.h
--- linux-2.4.23/include/linux/sched.h Fri Nov 28 19:26:21 2003
+++ linux-2.4.23-kp1/include/linux/sched.h Sat Dec 6 09:57:04 2003
@@ -429,6 +429,7 @@
#define PF_DUMPCORE 0x00000200 /* dumped core */
#define PF_SIGNALED 0x00000400 /* killed by a signal */
#define PF_MEMALLOC 0x00000800 /* Allocating memory */
+#define PF_MEMDIE 0x00001000 /* Killed for out-of-memory */
#define PF_FREE_PAGES 0x00002000 /* per process page freeing */
#define PF_NOIO 0x00004000 /* avoid generating further I/O */
diff -rauN linux-2.4.23/mm/oom_kill.c linux-2.4.23-kp1/mm/oom_kill.c
--- linux-2.4.23/mm/oom_kill.c Fri Nov 28 19:26:21 2003
+++ linux-2.4.23-kp1/mm/oom_kill.c Fri Dec 5 20:31:39 2003
@@ -21,8 +21,6 @@
#include <linux/swapctl.h>
#include <linux/timex.h>
-#if 0 /* Nothing in this file is used */
-
/* #define DEBUG */
/**
@@ -257,5 +255,3 @@
first = now;
count = 0;
}
-
-#endif /* Unused file */
diff -rauN linux-2.4.23/mm/vmscan.c linux-2.4.23-kp1/mm/vmscan.c
--- linux-2.4.23/mm/vmscan.c Fri Nov 28 19:26:21 2003
+++ linux-2.4.23-kp1/mm/vmscan.c Sat Dec 6 10:21:55 2003
@@ -649,13 +649,7 @@
failed_swapout = !swap_out(classzone);
} while (--tries);
- if (likely(current->pid != 1))
- break;
- if (!check_classzone_need_balance(classzone))
- break;
-
- __set_current_state(TASK_RUNNING);
- yield();
+ out_of_memory();
}
return 0;
*Kristian
_o)
/\\
_\_V
next prev parent reply other threads:[~2003-12-06 9:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Z6Iv-7O2-29@gated-at.bofh.it>
[not found] ` <Z8Ag-3BK-3@gated-at.bofh.it>
[not found] ` <Zbyn-23P-29@gated-at.bofh.it>
2003-12-05 13:05 ` oom killer in 2.4.23 Kristian Peters
2003-12-05 13:56 ` Robert L. Harris
2003-12-05 19:58 ` Andrea Arcangeli
2003-12-06 9:31 ` Kristian Peters [this message]
2003-12-09 14:21 ` Andrea Arcangeli
2003-12-09 14:52 ` Richard B. Johnson
2003-12-09 17:06 ` Andrea Arcangeli
2003-12-09 18:50 ` Kristian Peters
2003-12-05 22:38 ` Mike Fedyk
2003-12-05 22:56 ` Andrea Arcangeli
2003-12-04 16:12 Peter Bergmann
2003-12-04 17:02 ` Maciej Zenczykowski
2003-12-04 17:20 ` Guillermo Menguez Alvarez
2003-12-04 23:52 ` Andrea Arcangeli
2003-12-04 18:33 ` Peter Bergmann
2003-12-04 18:42 ` Jens Axboe
2003-12-04 20:38 ` Peter Bergmann
2003-12-04 20:28 ` Szakacsits Szabolcs
2003-12-04 23:58 ` Andrea Arcangeli
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=20031206103143.027ba4ec.kristian.peters@korseby.net \
--to=kristian.peters@korseby.net \
--cc=Robert.L.Harris@rdlg.net \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).