From: "John Fremlin" <vii@penguinpowered.com>
To: Stephen Tweedie <sct@redhat.com>
Cc: linux-mm@kvack.org
Subject: Re: [RFC] RSS guarantees and limits
Date: 22 Jun 2000 23:39:44 +0100 [thread overview]
Message-ID: <m2og4t9w7j.fsf@boreas.southchinaseas> (raw)
In-Reply-To: Stephen Tweedie's message of "Thu, 22 Jun 2000 22:19:23 +0100"
Stephen Tweedie <sct@redhat.com> writes:
> On Thu, Jun 22, 2000 at 07:00:54PM +0100, John Fremlin wrote:
> >
> > > - protect smaller apps from bigger memory hogs
> >
> > Why? Yes, it's very altruistic, very sportsmanlike, but giving small,
> > rarely used processes a form of social security is only going to
> > increase bureaucracy ;-)
>
> It is critically important that when under memory pressure, a
> system administrator can still log in and kill any runaway
> processes. The smaller apps in question here are system daemons
> such as init, inetd and telnetd, and user apps such as bash and
> ps. We _must_ be able to allow them to make at least some
> progress while the VM is under load.
I agree completely. It was one of the reasons I suggested that a
syscall like nice but giving info to the mm layer would be useful. In
general, small apps (xeyes,biff,gpm) don't deserve any special
treatment.
I also said that on a multiuser system it is important that one user
can't hog the system. In the case where it is impossible for a large
app to drop root privileges being root wouldn't help unless an
exception were made for admin caps.
The only general solution I can see is to give some process (groups) a
higher MM priority, by analogy with nice.
It is critically important that an admin can login to kill a swarm of
tiny runaway processes. A tiny program that forks every few seconds
can bring down a machine just as, if not more effectively than, a
couple of large runaways.
[...]
--
http://altern.org/vii
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-06-22 22:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-21 22:29 Rik van Riel
2000-06-22 18:00 ` John Fremlin
2000-06-22 19:12 ` Rik van Riel
2000-06-22 21:19 ` Stephen Tweedie
2000-06-22 21:37 ` Rik van Riel
2000-06-22 22:48 ` John Fremlin
2000-06-22 23:59 ` Stephen Tweedie
2000-06-23 16:08 ` John Fremlin
2000-06-22 22:39 ` John Fremlin [this message]
2000-06-22 23:27 ` Rik van Riel
2000-06-23 0:49 ` Ed Tomlinson
2000-06-23 13:45 ` Rik van Riel
2000-06-23 15:36 ` volodya
2000-06-23 15:52 ` John Fremlin
2000-06-24 11:22 ` Andrey Savochkin
2000-06-27 3:26 ` Stephen C. Tweedie
2000-06-22 14:41 [RFC] " frankeh
2000-06-22 15:31 ` Rik van Riel
2000-06-22 15:49 frankeh
2000-06-22 16:05 ` Rik van Riel
2000-06-22 16:22 frankeh
2000-06-22 16:38 ` Rik van Riel
2000-06-22 19:48 ` Jamie Lokier
2000-06-22 19:52 ` Rik van Riel
2000-06-22 20:00 ` Jamie Lokier
2000-06-22 20:07 ` Rik van Riel
2000-06-22 23:02 Mark_H_Johnson
2000-06-23 14:01 frankeh
2000-06-23 17:56 ` Stephen Tweedie
2000-06-23 18:07 frankeh
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=m2og4t9w7j.fsf@boreas.southchinaseas \
--to=vii@penguinpowered.com \
--cc=linux-mm@kvack.org \
--cc=sct@redhat.com \
/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