From: "Stephen C. Tweedie" <sct@redhat.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: riel@nl.linux.org, linux-mm@kvack.org
Subject: Re: [patch] memory hog protection
Date: Wed, 26 Apr 2000 11:53:07 +0100 [thread overview]
Message-ID: <20000426115307.C3792@redhat.com> (raw)
In-Reply-To: <390603EA.7DFC64BA@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Tue, Apr 25, 2000 at 04:45:30PM -0400
Hi,
On Tue, Apr 25, 2000 at 04:45:30PM -0400, Jeff Garzik wrote:
>
> ...dozen or so smaller processes which are far less important than the
> database server :)
That's exactly the property we need to avoid. In many cases, when
you have one large memory hog thrashing away, the one smaller process
which _really_ matters is the shell from which root is trying to sort
out the mess.
--Stephen
--
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/
prev parent reply other threads:[~2000-04-26 10:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-24 2:38 Rik van Riel
2000-04-24 4:53 ` Jeff Garzik
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 [this message]
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=20000426115307.C3792@redhat.com \
--to=sct@redhat.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox