Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 5 Oct 2001 18:16:02 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 5 Oct 2001 18:15:52 -0400 Received: from smtp9.xs4all.nl ([194.109.127.135]:7894 "EHLO smtp9.xs4all.nl") by vger.kernel.org with ESMTP id ; Fri, 5 Oct 2001 18:15:44 -0400 Date: Sat, 6 Oct 2001 00:16:11 +0200 (CEST) From: Seth Mos To: David Schwartz cc: Rik van Riel , Krzysztof Rusocki , linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: Re: %u-order allocation failed In-Reply-To: <20011005220627.AAA22897@shell.webmaster.com@whenever> 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 Fri, 5 Oct 2001, David Schwartz wrote: > > >The system is beafy enough to tolerate something mundane as this. It should > >definitely not die. > > A fork bomb with no limits attempts to create an infinite number of > processes. No system can be that beefy. I was refering to the mundane load of mongo.pl with 5 processes. Something the systems should withstand. If you have more then 10GB of database to access you would want it to work. I am not talking about a lot of processes but a lot of disk IO. I have just one box running SMP with highmem and that one is acting funny. All the other SMP ur Uni servers have absolutely no problems. Disable highmem and the problem goes away while halving your ram. That is not very efficient is it? Cheers - 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/