Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262623AbTIAGBq (ORCPT ); Mon, 1 Sep 2003 02:01:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262630AbTIAGBp (ORCPT ); Mon, 1 Sep 2003 02:01:45 -0400 Received: from nat-pool-bos.redhat.com ([66.187.230.200]:9072 "EHLO chimarrao.boston.redhat.com") by vger.kernel.org with ESMTP id S262623AbTIAGBn (ORCPT ); Mon, 1 Sep 2003 02:01:43 -0400 Date: Mon, 1 Sep 2003 02:01:35 -0400 (EDT) From: Rik van Riel X-X-Sender: riel@chimarrao.boston.redhat.com To: Marcelo Tosatti cc: Andrea Arcangeli , lkml Subject: Re: Andrea VM changes 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 Content-Length: 956 Lines: 24 On Sun, 31 Aug 2003, Marcelo Tosatti wrote: > Suppose you have a big fat hog leaking (lets say, netscape) allocating > pages at a slow pace. Now you have a decent well behaved app who is > allocating at a fast pace, and gets killed. > > The chance the well behaved app gets killed is big, right? Usually syslogd, which receives an error message from the network driver the moment memory fills up. The near-certain death of syslogd in OOM situations is why I wrote the OOM killer in the first place. -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan - 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/