From: Andreas Hartmann <andihartmann@freenet.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Kernel-Mailingliste <linux-kernel@vger.kernel.org>
Subject: Re: [2.4.18] Security: Process-Killer if machine get's out of memory
Date: Sun, 24 Mar 2002 18:24:12 +0100 [thread overview]
Message-ID: <3C9E0BBC.4030406@freenet.de> (raw)
In-Reply-To: <E16pBJE-0006hU-00@the-village.bc.nu>
Alan Cox wrote:
>>I've got a basic question:
>>Would it be possible to kill only the process which consumes the most
>>memory in the last delta t?
>>Or does somebody have a better idea?
>
>
> At the point you hit OOM every possible heuristic is simply handwaving that
> will work for a subset of the user base. Fix the real problem and it goes
> away.
This would and must be the first solution. I agree with you.
On the other hand - nobody is perfect and there can be such situations.
Why shouldn't the kernel be the ultimate checkpoint to prevent greater
damage? That's what I'm thinking.
It's not easy and it takes probably ressources (processor and RAM) to do
some
checks. The idea would be, to do such checks only when the memory-usage is
over a defined value, e.g. 60% or later. Best would be, if it would be
free configurable (to have the checks at all and at which point beginning).
I suggested a heuristic. Maybe, there are better ones. What I want to
say is, that I think that there should be a mechanism to detect and kill
a process as good as possible, which wants to have all the memory and
even more - before the memory is used to 100%.
Regards,
Andreas Hartmann
next prev parent reply other threads:[~2002-03-24 17:22 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-24 12:09 [2.4.18] Security: Process-Killer if machine get's out of memory andreas
[not found] ` <3C9DC6D0.3080606@wanadoo.fr>
2002-03-24 13:24 ` Andreas Hartmann
[not found] ` <3C9DD653.8090701@wanadoo.fr>
2002-03-24 13:36 ` Andreas Hartmann
2002-03-24 13:30 ` Rik van Riel
2002-03-24 14:08 ` Andreas Hartmann
2002-03-24 16:54 ` Alan Cox
2002-03-24 16:59 ` Andreas Hartmann
[not found] ` <3C9E48B8.9080707@ngforever.de>
2002-03-24 22:23 ` Andreas Hartmann
2002-03-24 15:58 ` Chris Swiedler
2002-03-24 16:57 ` Alan Cox
2002-03-24 16:59 ` Roy Sigurd Karlsbakk
2002-03-24 17:45 ` Rik van Riel
2002-03-24 17:57 ` Christian Bornträger
2002-03-24 18:01 ` Rik van Riel
2002-03-24 18:03 ` Bernd Petrovitsch
2002-03-24 18:23 ` Alan Cox
2002-03-24 18:37 ` Andreas Hartmann
2002-03-24 18:20 ` Alan Cox
2002-03-24 19:20 ` Itai Nahshon
2002-03-24 17:24 ` Andreas Hartmann [this message]
2002-03-24 18:22 ` Alan Cox
2002-03-24 18:23 ` Mr. James W. Laferriere
2002-03-24 19:49 ` Alan Cox
2002-03-24 19:48 ` Mr. James W. Laferriere
2002-03-24 20:39 ` Alan Cox
2002-03-24 18:32 ` Andreas Hartmann
2002-03-24 19:50 ` Alan Cox
2002-03-24 20:43 ` Paul P Komkoff Jr
2002-03-25 15:09 ` Rok Papež
2002-03-26 20:24 ` dean gaudet
2002-03-26 23:47 ` Alan Cox
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=3C9E0BBC.4030406@freenet.de \
--to=andihartmann@freenet.de \
--cc=alan@lxorguk.ukuu.org.uk \
--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