Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753466Ab0HYL5X (ORCPT ); Wed, 25 Aug 2010 07:57:23 -0400 Received: from thunk.org ([69.25.196.29]:40158 "EHLO thunker.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751435Ab0HYL5V (ORCPT ); Wed, 25 Aug 2010 07:57:21 -0400 Date: Wed, 25 Aug 2010 07:57:09 -0400 From: "Ted Ts'o" To: Peter Zijlstra Cc: David Rientjes , Jens Axboe , Andrew Morton , Neil Brown , Alasdair G Kergon , Chris Mason , Steven Whitehouse , Jan Kara , Frederic Weisbecker , "linux-raid@vger.kernel.org" , "linux-btrfs@vger.kernel.org" , "cluster-devel@redhat.com" , "linux-ext4@vger.kernel.org" , "reiserfs-devel@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [patch 1/5] mm: add nofail variants of kmalloc kcalloc and kzalloc Message-ID: <20100825115709.GD4453@thunk.org> Mail-Followup-To: Ted Ts'o , Peter Zijlstra , David Rientjes , Jens Axboe , Andrew Morton , Neil Brown , Alasdair G Kergon , Chris Mason , Steven Whitehouse , Jan Kara , Frederic Weisbecker , "linux-raid@vger.kernel.org" , "linux-btrfs@vger.kernel.org" , "cluster-devel@redhat.com" , "linux-ext4@vger.kernel.org" , "reiserfs-devel@vger.kernel.org" , "linux-kernel@vger.kernel.org" References: <1282656558.2605.2742.camel@laptop> <4C73CA24.3060707@fusionio.com> <20100825112433.GB4453@thunk.org> <1282736132.2605.3563.camel@laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1282736132.2605.3563.camel@laptop> User-Agent: Mutt/1.5.20 (2009-06-14) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: tytso@thunk.org X-SA-Exim-Scanned: No (on thunker.thunk.org); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1076 Lines: 25 On Wed, Aug 25, 2010 at 01:35:32PM +0200, Peter Zijlstra wrote: > On Wed, 2010-08-25 at 07:24 -0400, Ted Ts'o wrote: > > Part of the problem is that we have a few places in the kernel where > > failure is really not an option --- or rather, if we're going to fail > > while we're in the middle of doing a commit, our choices really are > > (a) retry the loop in the jbd layer (which Andrew really doesn't > > like), (b) keep our own private cache of free memory so we don't fail > > and/or loop, (c) fail the file system and mark it read-only, or (d) > > panic. > > d) do the allocation before you're committed to going fwd and can still > fail and back out. Sure in some cases that can be done, but the commit has to happen at some point, or we run out of journal space, at which point we're back to (c) or (d). - Ted -- 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/