From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: [patch 4/6] jbd: remove dependency on __GFP_NOFAIL Date: Mon, 23 Aug 2010 15:11:29 -0700 Message-ID: <20100823151129.433875d9.akpm@linux-foundation.org> References: <20100817095103.GA3557@quack.suse.cz> <20100823122813.1ffa3f2e.akpm@linux-foundation.org> <20100823220347.GB3380@quack.suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: David Rientjes , linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org To: Jan Kara Return-path: Received: from smtp1.linux-foundation.org ([140.211.169.13]:56335 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754309Ab0HWWLj (ORCPT ); Mon, 23 Aug 2010 18:11:39 -0400 In-Reply-To: <20100823220347.GB3380@quack.suse.cz> Sender: linux-ext4-owner@vger.kernel.org List-ID: On Tue, 24 Aug 2010 00:03:47 +0200 Jan Kara wrote: > So do > you think that we should keep __GFP_NOFAIL as long as all callers are not > able to handle allocation failures in more reasonable way? The concept should be encapsulated in _some_ centralised fashion. Helper functions would work as well as __GFP_NOFAIL, and will move any runtime cost away from the good code and push it onto the bad code.