Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932261AbVJCO6g (ORCPT ); Mon, 3 Oct 2005 10:58:36 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750987AbVJCO6g (ORCPT ); Mon, 3 Oct 2005 10:58:36 -0400 Received: from quark.didntduck.org ([69.55.226.66]:15240 "EHLO quark.didntduck.org") by vger.kernel.org with ESMTP id S1750971AbVJCO6f (ORCPT ); Mon, 3 Oct 2005 10:58:35 -0400 Message-ID: <4341476A.80809@didntduck.org> Date: Mon, 03 Oct 2005 10:59:54 -0400 From: Brian Gerst User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Paul Mundt CC: mingo@elte.hu, linux-kernel@vger.kernel.org Subject: Re: [RFC] mempool_alloc() pre-allocated object usage References: <20051003143634.GA1702@nokia.com> In-Reply-To: <20051003143634.GA1702@nokia.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 679 Lines: 17 Paul Mundt wrote: > The downside to this is that some people may be expecting that > pre-allocated elements are used as reserve space for when regular > allocations aren't possible. In which case, this would break that > behaviour. This is the original intent of the mempool. There must be objects in reserve so that the machine doesn't deadlock on critical allocations (ie. disk writes) under memory pressure. -- Brian Gerst - 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/