Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757369AbXISUre (ORCPT ); Wed, 19 Sep 2007 16:47:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753058AbXISUrW (ORCPT ); Wed, 19 Sep 2007 16:47:22 -0400 Received: from e6.ny.us.ibm.com ([32.97.182.146]:43140 "EHLO e6.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751410AbXISUrU (ORCPT ); Wed, 19 Sep 2007 16:47:20 -0400 Subject: Re: [PATCH] JBD slab cleanups From: Mingming Cao Reply-To: cmm@us.ibm.com To: Dave Kleikamp Cc: Andrew Morton , Christoph Hellwig , Badari Pulavarty , Christoph Lameter , linux-fsdevel , ext4 development , lkml In-Reply-To: <1190230126.6504.5.camel@norville.austin.ibm.com> References: <20070902152801.GA19962@infradead.org> <20070903134043.GB28962@infradead.org> <20070903193308.GA7771@infradead.org> <1189796027.3841.6.camel@localhost.localdomain> <1190057391.3845.22.camel@localhost.localdomain> <1190066466.31220.5.camel@dyn9047017100.beaverton.ibm.com> <1190069851.6725.6.camel@localhost.localdomain> <20070918090407.GA671@infradead.org> <1190133347.3819.6.camel@localhost.localdomain> <1190138690.6528.23.camel@norville.austin.ibm.com> <1190163601.3819.15.camel@localhost.localdomain> <20070918191920.a2130a3c.akpm@linux-foundation.org> <1190229352.4318.12.camel@localhost.localdomain> <1190229991.6504.3.camel@norville.austin.ibm.com> <1190230126.6504.5.camel@norville.austin.ibm.com> Content-Type: text/plain Organization: IBM Linux Technology Center Date: Wed, 19 Sep 2007 13:47:16 -0700 Message-Id: <1190234836.4318.20.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.8.0 (2.8.0-33.el5) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1068 Lines: 28 On Wed, 2007-09-19 at 19:28 +0000, Dave Kleikamp wrote: > On Wed, 2007-09-19 at 14:26 -0500, Dave Kleikamp wrote: > > On Wed, 2007-09-19 at 12:15 -0700, Mingming Cao wrote: > > > > > Here is the patch to clean up __GFP_NOFAIL flag in jbd/jbd2. In all > > > cases except one handles memory allocation failure so I get rid of those > > > GFP_NOFAIL flags. > > > > > > Also, shouldn't we use GFP_KERNEL instead of GFP_NOFS flag for kmalloc > > > in jbd/jbd2? I will send a separate patch to cleanup that. > > > > No. GFP_NOFS avoids deadlock. It prevents the allocation from making > > recursive calls back into the file system that could end up blocking on > > jbd code. > > Oh, I see your patch now. You mean use GFP_NOFS instead of > GFP_KERNEL. :-) OK then. > oops, I did mean what you say here.:-) > > Shaggy - 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/