From: "J . A . Magallon" <jamagallon@able.es>
To: Jussi Laako <jussi@jlaako.pp.fi>
Cc: Marc Mutz <Marc@Mutz.com>, linux-kernel@vger.kernel.org
Subject: Re: VM problem (2.4.0-test11)
Date: Wed, 13 Dec 2000 00:41:19 +0100 [thread overview]
Message-ID: <20001213004119.A779@werewolf.able.es> (raw)
In-Reply-To: <3A36A163.3F01277D@jlaako.pp.fi> <3A36ADB8.3CE36940@Mutz.com> <3A36B3E5.CF9FC31D@jlaako.pp.fi>
In-Reply-To: <3A36B3E5.CF9FC31D@jlaako.pp.fi>; from jussi@jlaako.pp.fi on Wed, Dec 13, 2000 at 00:25:25 +0100
On Wed, 13 Dec 2000 00:25:25 Jussi Laako wrote:
> Marc Mutz wrote:
> >
> > Just to not miss the obvious: You know about ulimit(3)?
>
> Yes, but it doesn't stop deadlocks caused by kernel's VM system going
> wild... I think that no matter what user process does, root should be always
> able to stop it. User process should never be able to render whole system
> unusable.
>
That is just some issue that was discussed in this list recently. Look in the
list
for 'oom killer' subjects.
There are various patches-ways-to-do available, kernel gurus are still working
on it...
(leave always some 4% of mem for root, kill some process when mem is exhausted,
which one to kill...)
--
Juan Antonio Magallon Lacarta #> cd /pub
mailto:jamagallon@able.es #> more beer
Linux werewolf 2.2.18-aa1 #1 SMP Mon Dec 11 21:26:28 CET 2000 i686
-
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-12-13 0:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-12 22:06 VM problem (2.4.0-test11) Jussi Laako
2000-12-12 22:59 ` Marc Mutz
2000-12-12 23:25 ` Jussi Laako
2000-12-12 23:41 ` J . A . Magallon [this message]
2000-12-13 13:55 ` Ragnar Hojland Espinosa
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=20001213004119.A779@werewolf.able.es \
--to=jamagallon@able.es \
--cc=Marc@Mutz.com \
--cc=jussi@jlaako.pp.fi \
--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