From: Rik van Riel <riel@conectiva.com.br>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Andrew Morton <akpm@digeo.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: 2.5.44-mm6
Date: Tue, 29 Oct 2002 15:28:00 -0200 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.44L.0210291526560.1697-100000@imladris.surriel.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1021029065944.6113B-100000@gatekeeper.tmr.com>
On Tue, 29 Oct 2002, Bill Davidsen wrote:
> On Mon, 28 Oct 2002, Andrew Morton wrote:
> > Rik van Riel wrote:
> > > Just let me know if you're interested in my load control mechanism
> > > and I'll send it to you.
> > It would also be interesting to know if we really care?
>
> I think there is a need for keeping an overloaded machine in some way
> usable, not because anyone is really running it that way, but because
> the sysadmin needs a way to determine why a correctly sized machine is
> suddenly seeing a high load.
Indeed, it's a stability thing, not a performance thing.
It's Not Good(tm) to have a system completely crap out because
of a load spike. Instead it should survive the load spike and
go on with life.
Rik
--
Bravely reimplemented by the knights who say "NIH".
http://www.surriel.com/ http://distro.conectiva.com/
Current spamtrap: <a href=mailto:"october@surriel.com">october@surriel.com</a>
--
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-mm.org/
prev parent reply other threads:[~2002-10-29 17:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 6:06 2.5.44-mm6 Andrew Morton
2002-10-28 2:24 ` 2.5.44-mm6 Rob Landley
2002-10-28 7:31 ` 2.5.44-mm6 Andrew Morton
2002-10-28 2:41 ` 2.5.44-mm6 Rob Landley
2002-10-28 12:53 ` 2.5.44-mm6 Rik van Riel
2002-10-28 17:18 ` 2.5.44-mm6 Andrew Morton
2002-10-29 12:02 ` 2.5.44-mm6 Bill Davidsen
2002-10-29 17:28 ` Rik van Riel [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=Pine.LNX.4.44L.0210291526560.1697-100000@imladris.surriel.com \
--to=riel@conectiva.com.br \
--cc=akpm@digeo.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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