Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 29 Oct 2002 12:22:06 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 29 Oct 2002 12:22:06 -0500 Received: from 3-090.ctame701-1.telepar.net.br ([200.193.161.90]:16037 "EHLO 3-090.ctame701-1.telepar.net.br") by vger.kernel.org with ESMTP id ; Tue, 29 Oct 2002 12:22:05 -0500 Date: Tue, 29 Oct 2002 15:28:00 -0200 (BRST) From: Rik van Riel X-X-Sender: riel@imladris.surriel.com To: Bill Davidsen cc: Andrew Morton , lkml , Subject: Re: 2.5.44-mm6 In-Reply-To: Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1165 Lines: 29 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: october@surriel.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/