From: David Rientjes Subject: Re: [patch 1/5] mm: add nofail variants of kmalloc kcalloc and kzalloc Date: Wed, 25 Aug 2010 13:59:55 -0700 (PDT) Message-ID: References: <1282656558.2605.2742.camel@laptop> <4C73CA24.3060707@fusionio.com> <20100825112433.GB4453@thunk.org> <1282736132.2605.3563.camel@laptop> <20100825115709.GD4453@thunk.org> <1282740516.2605.3644.camel@laptop> <20100825132417.GQ31488@dastard> <1282743342.2605.3707.camel@laptop> <20100825205342.GG4453@thunk.org> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII To: "Ted Ts'o" , Peter Zijlstra , Dave Chinner , Jens Axboe , Andrew Morton , Ne Return-path: Received: from smtp-out.google.com ([74.125.121.35]:50136 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754254Ab0HYVAC (ORCPT ); Wed, 25 Aug 2010 17:00:02 -0400 In-Reply-To: <20100825205342.GG4453@thunk.org> Sender: linux-ext4-owner@vger.kernel.org List-ID: On Wed, 25 Aug 2010, Ted Ts'o wrote: > A pool of free pages which is reserved for routines that are doing > page cleaning would probably also be a good idea. Maybe that's just > retrying with GFP_ATOMIC if a normal allocation fails, or maybe we > need our own special pool, or maybe we need to dynamically resize the > GFP_ATOMIC pool based on how many subsystems might need to use it.... > PF_MEMALLOC is used for those tasks, not GFP_ATOMIC.