Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 8 Oct 2001 19:54:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 8 Oct 2001 19:54:42 -0400 Received: from artax.karlin.mff.cuni.cz ([195.113.31.125]:59142 "EHLO artax.karlin.mff.cuni.cz") by vger.kernel.org with ESMTP id ; Mon, 8 Oct 2001 19:54:34 -0400 Date: Tue, 9 Oct 2001 01:54:49 +0200 (CEST) From: Mikulas Patocka To: Linus Torvalds cc: Alan Cox , Rik van Riel , Alex Bligh - linux-kernel , Krzysztof Rusocki , linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: Re: %u-order allocation failed 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 On Mon, 8 Oct 2001, Linus Torvalds wrote: > > On Tue, 9 Oct 2001, Mikulas Patocka wrote: > > > > Linus, what do you think: is it OK if fork randomly fails with very small > > probability or not? > > I've never seen it, I've never heard it reported, and I _know_ that > vmalloc() causes slowdowns. > > In short, I'm not switching to a vmalloc() fork. The patch uses buddy by default and does vmalloc only if buddy fails. Slowdown is not an issue here. Mikulas - 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/