Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267536AbUJGSqc (ORCPT ); Thu, 7 Oct 2004 14:46:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267709AbUJGSpp (ORCPT ); Thu, 7 Oct 2004 14:45:45 -0400 Received: from odpn1.odpn.net ([212.40.96.53]:60077 "EHLO odpn1.odpn.net") by vger.kernel.org with ESMTP id S267772AbUJGSnp (ORCPT ); Thu, 7 Oct 2004 14:43:45 -0400 To: Marcelo Tosatti Cc: Michael Buesch , linux kernel mailing list Subject: Re: [2.4] 0-order allocation failed References: <200410071318.21091.mbuesch@freenet.de> <20041007151518.GA14614@logos.cnet> <200410071917.40896.mbuesch@freenet.de> <20041007153929.GB14614@logos.cnet> <20041007164221.GD14614@logos.cnet> From: "Gabor Z. Papp" Date: Thu, 07 Oct 2004 20:43:39 +0200 Message-ID: User-Agent: Gnus/5.110003 (No Gnus v0.3) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Authenticated: gzp1 odpn1.odpn.net a3085bdc7b32ae4d7418f70f85f7cf5f Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 698 Lines: 18 * Marcelo Tosatti : | > There is really no way to run 2.4 without swap? | | Nope. Any kernel can't. The thing is the system overcommits | memory (it allows applications to allocate more memory than the system | is able to handle). Okay, then whats the required minimum swap size that needed to avoid such crashes? In the case when the system is in the ram, quite funny to allocate a swap file on the ramdisk anyway... - 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/