From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail138.messagelabs.com (mail138.messagelabs.com [216.82.249.35]) by kanga.kvack.org (Postfix) with ESMTP id 948EB8D0080 for ; Wed, 17 Nov 2010 02:20:10 -0500 (EST) Subject: Re: Propagating GFP_NOFS inside __vmalloc() Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Andreas Dilger In-Reply-To: <20101116141130.b20a8a8d.akpm@linux-foundation.org> Date: Wed, 17 Nov 2010 01:18:27 -0600 Content-Transfer-Encoding: 7bit Message-Id: References: <1289421759.11149.59.camel@oralap> <20101111120643.22dcda5b.akpm@linux-foundation.org> <1289512924.428.112.camel@oralap> <20101111142511.c98c3808.akpm@linux-foundation.org> <1289840500.13446.65.camel@oralap> <20101116141130.b20a8a8d.akpm@linux-foundation.org> Sender: owner-linux-mm@kvack.org To: Andrew Morton Cc: David Rientjes , "Ricardo M. Correia" , linux-mm@kvack.org, Brian Behlendorf List-ID: On 2010-11-16, at 16:11, Andrew Morton wrote: > On Mon, 15 Nov 2010 13:28:54 -0800 (PST) > David Rientjes wrote: > >> - avoid doing anything other than GFP_KERNEL allocations for __vmalloc(): >> the only current users are gfs2, ntfs, and ceph (the page allocator >> __vmalloc() can be discounted since it's done at boot and GFP_ATOMIC >> here has almost no chance of failing since the size is determined based >> on what is available). > > ^^ this > > Using vmalloc anywhere is lame. I agree. What we really want is 1MB kmalloc() to work... :-/ Cheers, Andreas -- Andreas Dilger Lustre Technical Lead Oracle Corporation Canada Inc. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/ Don't email: email@kvack.org