Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 24 Mar 2002 12:00:06 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 24 Mar 2002 11:59:56 -0500 Received: from mustard.heime.net ([194.234.65.222]:41625 "EHLO mustard.heime.net") by vger.kernel.org with ESMTP id ; Sun, 24 Mar 2002 11:59:52 -0500 Date: Sun, 24 Mar 2002 17:59:38 +0100 (CET) From: Roy Sigurd Karlsbakk To: Alan Cox cc: andreas , Kernel-Mailingliste Subject: Re: [2.4.18] Security: Process-Killer if machine get's out of memory In-Reply-To: Message-ID: 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 On Sun, 24 Mar 2002, Alan Cox wrote: > > I've got a basic question: > > Would it be possible to kill only the process which consumes the most > > memory in the last delta t? > > Or does somebody have a better idea? > > At the point you hit OOM every possible heuristic is simply handwaving that > will work for a subset of the user base. Fix the real problem and it goes > away. My box doesn't OOM, the worst case (which I've never seen happen) is > a task being killed by a stack growth failing to get memory. Would it hard to do some memory allocation statistics, so if some process at one point (as rsync did) goes crazy eating all memory, that would be detected? I'm quite sure other OSes have similar funcitonality, such as AIX roy -- Roy Sigurd Karlsbakk, Datavaktmester Computers are like air conditioners. They stop working when you open Windows. - 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/