From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: riel@nl.linux.org
Cc: linux-mm@kvack.org
Subject: Re: [patch] memory hog protection
Date: Mon, 24 Apr 2000 00:53:39 -0400 [thread overview]
Message-ID: <3903D353.D98969B7@mandrakesoft.com> (raw)
In-Reply-To: Pine.LNX.4.21.0004232255530.1852-100000@duckman.conectiva
Rik van Riel wrote:
> the patch below changes the mm->swap_cnt assignment to put
> memory hogs at a disadvantage to programs with a smaller
> RSS.
[...]
There are many classes of problems where preserving interactivity at the
expense of a resource hog is a bad not good idea. Think of obscure
situations like database servers for example :)
--
Jeff Garzik | Nothing cures insomnia like the
Building 1024 | realization that it's time to get up.
MandrakeSoft, Inc. | -- random fortune
--
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-04-24 4:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-24 2:38 [patch] memory hog protection Rik van Riel
2000-04-24 4:53 ` Jeff Garzik [this message]
2000-04-24 7:30 ` Arjan van de Ven
2000-04-24 11:01 ` Rik van Riel
2000-04-25 20:45 ` Jeff Garzik
2000-04-26 10:53 ` Stephen C. Tweedie
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=3903D353.D98969B7@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=linux-mm@kvack.org \
--cc=riel@nl.linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.