Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754271Ab0HZBag (ORCPT ); Wed, 25 Aug 2010 21:30:36 -0400 Received: from smtp103.prem.mail.ac4.yahoo.com ([76.13.13.42]:39223 "HELO smtp103.prem.mail.ac4.yahoo.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1752877Ab0HZBab (ORCPT ); Wed, 25 Aug 2010 21:30:31 -0400 X-Yahoo-SMTP: _Dag8S.swBC1p4FJKLCXbs8NQzyse1SYSgnAbY0- X-YMail-OSG: zuPqxDMVM1kXH64xUYCr_Ew159XaW.3MJlXHbdTiWfT5obI zXF9ingyPgJpuGLuepsTKz2WgN8ShYOjOzmaYyzlAVyABDQISXlem0akC0Wa LhEch3nCiYVEWSyo4ucnFfRK.KRv44Iz9fMwyCBe7ARCU70N8KXS9RrQffpF k.CA6mtVg_wIdkv_cspHw9gnSPFDgTyg8ZaO5ftNI9QHRk8gbh4JnyumJtMe pygiOglUefnWyViN15vmISUvRhJNP X-Yahoo-Newman-Property: ymail-3 Date: Wed, 25 Aug 2010 20:30:24 -0500 (CDT) From: Christoph Lameter X-X-Sender: cl@router.home To: David Rientjes cc: Peter Zijlstra , Dave Chinner , "Ted Ts'o" , 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 In-Reply-To: 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> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 850 Lines: 25 On Wed, 25 Aug 2010, David Rientjes wrote: > On Wed, 25 Aug 2010, Christoph Lameter wrote: > > > If the higher order fails in slub then an order 0 alloc is attempted > > without __GFP_NORETRY. In both cases the nofail behavior of the page > > allocator determines the outcode. > > > > Right, I thought you said the slab layer passes __GFP_NOFAIL when there's > no objects available. Yes, the slab layer calls the page allocator when there are no objects available and passes the __GFP_NOFAIL that the user may have set in the call to the page allocator. Why then add new functions that do the same? -- 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/