Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 7 Oct 2001 10:08:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 7 Oct 2001 10:07:54 -0400 Received: from lightning.swansea.linux.org.uk ([194.168.151.1]:37125 "EHLO the-village.bc.nu") by vger.kernel.org with ESMTP id ; Sun, 7 Oct 2001 10:07:41 -0400 Subject: Re: %u-order allocation failed To: mikulas@artax.karlin.mff.cuni.cz (Mikulas Patocka) Date: Sun, 7 Oct 2001 15:12:37 +0100 (BST) Cc: alan@lxorguk.ukuu.org.uk (Alan Cox), riel@conectiva.com.br (Rik van Riel), kszysiu@main.braxis.co.uk (Krzysztof Rusocki), linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org In-Reply-To: from "Mikulas Patocka" at Oct 07, 2001 02:28:17 PM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: Alan Cox Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > Yes - you can run out of vmalloc space. But you run out of it only when > you create too many processes (8192), load too many modules etc. If > someone needs to put such heavy load on linux, we can expect that he is > not a luser and he knows how to increase size of vmalloc space. Not just that - you get fragmentation of it which leads you back to the same situation as kmalloc except that with the guard pages you fragment the address space more. Alan - 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/