From: Giuliano Pochini <pochini@shiny.it>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Killing/balancing processes when overcommited
Date: Fri, 13 Sep 2002 15:02:21 +0200 (CEST) [thread overview]
Message-ID: <XFMail.20020913150221.pochini@shiny.it> (raw)
In-Reply-To: <3D81C3EF.9509A4D0@aitel.hist.no>
> This is hard to setup, and has the some weaknesses:
> 1. You worry only about apps you _know_. But the guy who got
> his netscape or make -j killed will rename his
> copies of these apps to something else so your carefully
> set up oom killer won't know what is running.
> (How much memory is the "mybrowser" app supposed to use?)
> Or he'll get another software package that you haven't heard of.
>
> 2. Lots and lots of people running netscapes using
> only 70M each will still be too much. Think of
> a university with xterms and then they all
> goes to cnn.com or something for the latest news
> about some large event.
>
> Even nice well-behaved apps
> is bad when there is unusually many of them. [...]
That's obvious. The point is that the sysadmin should be
able to hint the oom killer as much as possible.
The current linux/mm/oom_kill.c:badness() takes into account
many factors. The sysadmin should be able to affect the
badness calculation on process/user/something basis.
Bye.
next prev parent reply other threads:[~2002-09-13 12:57 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 19:00 Killing/balancing processes when overcommited Jim Sibley
2002-09-12 19:08 ` Thunder from the hill
2002-09-12 20:35 ` Alan Cox
2002-09-12 20:43 ` Thunder from the hill
2002-09-12 20:55 ` Alan Cox
2002-09-12 21:15 ` Thunder from the hill
2002-09-12 21:22 ` Jesse Pollard
2002-09-12 23:08 ` Alan Cox
2002-09-12 23:12 ` Thunder from the hill
2002-09-12 21:19 ` Jesse Pollard
2002-09-12 21:56 ` Thunder from the hill
2002-09-13 7:51 ` Giuliano Pochini
2002-09-13 10:17 ` Thunder from the hill
2002-09-12 19:09 ` Rik van Riel
2002-09-13 8:05 ` Giuliano Pochini
2002-09-13 10:54 ` Helge Hafting
2002-09-13 13:02 ` Giuliano Pochini [this message]
2002-09-13 16:40 ` Gerhard Mack
2002-09-13 20:23 ` Timothy D. Witham
-- strict thread matches above, loose matches on Subject: below --
2002-09-13 21:13 Jim Sibley
2002-09-13 22:31 ` Timothy D. Witham
2002-09-13 22:38 ` Timothy D. Witham
2002-09-13 22:44 ` Rik van Riel
2002-09-13 23:12 ` Timothy D. Witham
2002-09-16 7:29 ` Helge Hafting
2002-09-16 14:03 ` Rik van Riel
2002-09-16 18:49 ` Timothy D. Witham
2002-09-16 19:11 ` Rik van Riel
2002-09-16 20:27 ` Timothy D. Witham
2002-09-14 0:23 ` Jim Sibley
2002-09-12 18:14 Jim Sibley
2002-09-11 18:08 Jim Sibley
2002-09-11 18:27 ` Jurriaan
2002-09-12 8:26 ` Helge Hafting
2002-09-11 21:44 ` Alan Cox
2002-09-12 7:06 ` Tim Connors
2002-09-12 7:25 ` Giuliano Pochini
2002-09-12 16:02 ` Rik van Riel
2002-09-12 18:30 ` Thunder from the hill
2002-09-13 8:17 ` Giuliano Pochini
2002-09-13 10:22 ` Thunder from the hill
2002-09-13 12:53 ` Denis Vlasenko
2002-09-13 12:54 ` 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=XFMail.20020913150221.pochini@shiny.it \
--to=pochini@shiny.it \
--cc=helgehaf@aitel.hist.no \
--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).