Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 26 Mar 2001 16:36:27 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 26 Mar 2001 16:36:17 -0500 Received: from mozart.stat.wisc.edu ([128.105.5.24]:23819 "EHLO mozart.stat.wisc.edu") by vger.kernel.org with ESMTP id ; Mon, 26 Mar 2001 16:36:08 -0500 To: Jonathan Morton Cc: Martin Dalecki , Rik van Riel , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] OOM handling In-Reply-To: <3ABDF8A6.7580BD7D@evision-ventures.com> From: buhr@stat.wisc.edu (Kevin Buhr) In-Reply-To: Jonathan Morton's message of "Sun, 25 Mar 2001 17:36:21 +0100" Date: 26 Mar 2001 15:34:31 -0600 Message-ID: Lines: 17 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 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 Jonathan Morton writes: > > Understood - my Physics courses covered this as well, but not using the > word "normalise". Be that as it may, Martin's comments about normalizing are nonsense. Rik's killer (at least in 2.4.3-pre7) produces a badness value that's a product of badness factors of various units. It then uses these products only for relative comparisons, choosing the process with maximum badness product to kill. No normalization is necessary, nor would it have any effect. The reason a 256 Meg process on a 1 Gig machine was being killed had nothing to do with normalization---it was a bug where the OOM killer was being called long before we were reduced to last resorts. Kevin - 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/