From: Martin Dalecki <dalecki@evision-ventures.com>
To: Jonathan Morton <chromi@cyberspace.org>
Cc: Rogier Wolff <R.E.Wolff@BitWizard.nl>, linux-kernel@vger.kernel.org
Subject: Re: OOM killer???
Date: Tue, 27 Mar 2001 15:24:16 +0200 [thread overview]
Message-ID: <3AC09480.E8317507@evision-ventures.com> (raw)
In-Reply-To: <l03130332b6e632432b9f@[192.168.239.101]>
Jonathan Morton wrote:
>
> >Out of Memory: Killed process 117 (sendmail).
> >
> >What we did to run it out of memory, I don't know. But I do know that
> >it shouldn't be killing one process more than once... (the process
> >should not exist after one try...)
>
> This is a known bug in the Out-of-Memory handler, where it does not count the buffer and cache memory as "free" (it should), causing premature OOM killing. It is, however, normal for the OOM killer to attempt to kill a process more than once - it takes a few scheduler cycles for the SIGKILL to actually reach the process and take effect.
>
> Also, it probably shouldn't have killed Sendmail, since that is usually a long-running, low-UID (and important) process. The OOM-kill selector is another thing that wants fixing, and my patch contains a *very rough* beginning to this.
>
> The following patch should solve your problem for now, until a more detailed fix (which also clears up many other problems) is available in the stable kernel.
>
> Alan and/or Linus may wish to apply this patch too...
>
> (excerpt from my original patch from Saturday follows)
>
> --- start ---
> diff -u linux-2.4.1.orig/mm/oom_kill.c linux/mm/oom_kill.c
> --- linux-2.4.1.orig/mm/oom_kill.c Tue Nov 14 18:56:46 2000
> +++ linux/mm/oom_kill.c Sat Mar 24 20:35:20 2001
> @@ -76,7 +76,9 @@
> run_time = (jiffies - p->start_time) >> (SHIFT_HZ + 10);
>
> points /= int_sqrt(cpu_time);
> - points /= int_sqrt(int_sqrt(run_time));
> +
> + /* Long-running processes are *very* important, so don't take the 4th root */
> + points /= run_time;
>
> /*
> * Niced processes are most likely less important, so double
> @@ -93,6 +95,10 @@
> p->uid == 0 || p->euid == 0)
> points /= 4;
>
> + /* Much the same goes for processes with low UIDs */
> + if(p->uid < 100 || p->euid < 100)
> + points /= 2;
> +
Plase change to 100 to 500 - this would make it consistant with
the useradd command, which starts adding new users at the UID 500
next prev parent reply other threads:[~2001-03-27 13:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-27 10:59 OOM killer??? Rogier Wolff
2001-03-27 12:14 ` Jonathan Morton
2001-03-27 13:24 ` Martin Dalecki [this message]
2001-03-27 15:31 ` Jonathan Lundell
2001-03-27 16:07 ` Config bug? In 2.2.19 CONFIG_RTL8139 depends on CONFIG_EXPERIMENTAL Greg Ingram
2001-03-27 16:14 ` Jeff Garzik
2001-03-27 16:37 ` [PATCH] 2.2.19 drivers/net/Config.in Greg Ingram
2001-03-27 18:08 ` OOM killer??? Ingo Oeser
2001-03-27 19:07 ` Martin Dalecki
2001-03-27 19:55 ` Andreas Dilger
2001-03-27 21:13 ` Andreas Rogge
2001-03-27 18:37 ` Jonathan Morton
2001-03-27 13:57 ` Jonathan Morton
[not found] <200103282138.f2SLcT824292@webber.adilger.int>
2001-03-29 9:29 ` Dr. Michael Weller
2001-03-29 11:01 ` Guest section DW
2001-03-29 12:02 ` Sean Hunter
2001-03-29 12:57 ` Guest section DW
2001-03-29 15:41 ` David Konerding
2001-03-29 17:52 ` David Lang
2001-03-30 2:26 ` Michael Peddemors
2001-03-30 14:48 ` J. Scott Kasten
2001-03-29 17:21 ` Stephen Satchell
2001-03-29 13:53 ` Szabolcs Szakacsits
2001-03-29 15:01 ` Dr. Michael Weller
2001-03-29 16:29 ` Szabolcs Szakacsits
2001-03-29 16:51 ` Szabolcs Szakacsits
-- strict thread matches above, loose matches on Subject: below --
2001-03-29 16:22 Jesse Pollard
2001-03-29 19:20 Jesse Pollard
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=3AC09480.E8317507@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=R.E.Wolff@BitWizard.nl \
--cc=chromi@cyberspace.org \
--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