Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 22 Mar 2001 18:27:00 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 22 Mar 2001 18:26:50 -0500 Received: from nat-pool.corp.redhat.com ([199.183.24.200]:43875 "EHLO devserv.devel.redhat.com") by vger.kernel.org with ESMTP id ; Thu, 22 Mar 2001 18:26:42 -0500 Message-ID: <3ABA8B02.F28B333A@redhat.com> Date: Thu, 22 Mar 2001 18:30:10 -0500 From: Doug Ledford X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.17-11 i686) X-Accept-Language: en MIME-Version: 1.0 To: Alan Cox CC: Stephen Clouse , Guest section DW , Rik van Riel , "Patrick O'Rourke" , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] Prevent OOM from killing init In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Alan Cox wrote: > > > > How do you return an out of memory error to a C program that is out of memory > > > due to a stack growth fault. There is actually not a language construct for it > > > > Simple, you reclaim a few of those uptodate buffers. My testing here has > > If you have reclaimable buffers you are not out of memory. If oom is triggered > in that state it is a bug. If you are complaining that the oom killer triggers > at the wrong time then thats a completely unrelated issue. Ummm, yeah, that would pretty much be the claim. Real easy to reproduce too. Take your favorite machine with lots of RAM, run just a handful of startup process and system daemons, then log in on a few terminals and do: while true; do bonnie -s (1/2 ram); done Pretty soon, system daemons will start to die. -- Doug Ledford http://people.redhat.com/dledford Please check my web site for aic7xxx updates/answers before e-mailing me about problems - 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/