From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753949Ab0ECJ3N (ORCPT ); Mon, 3 May 2010 05:29:13 -0400 Received: from mx1.redhat.com ([209.132.183.28]:64700 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753672Ab0ECJ3J (ORCPT ); Mon, 3 May 2010 05:29:09 -0400 Message-ID: <4BDE9753.1080106@redhat.com> Date: Mon, 03 May 2010 12:28:51 +0300 From: Avi Kivity User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100330 Fedora/3.0.4-1.fc12 Thunderbird/3.0.4 MIME-Version: 1.0 To: Jiri Slaby CC: Changli Gao , Tetsuo Handa , akpm@linux-foundation.org, paulmck@linux.vnet.ibm.com, adobriyan@gmail.com, mingo@elte.hu, peterz@infradead.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] fs: use kmalloc() to allocate fdmem if possible References: <1272818776-7729-1-git-send-email-xiaosuo@gmail.com> <4BDDB6E9.4060703@redhat.com> <201005030915.FCD09385.FFHVOMJtSLOFQO@I-love.SAKURA.ne.jp> <4BDE67DA.4080004@redhat.com> <4BDE7E66.8030509@redhat.com> <4BDE8E24.5050200@redhat.com> <4BDE914C.6080504@suse.cz> <4BDE94C8.9000108@redhat.com> <4BDE95F2.1020506@suse.cz> In-Reply-To: <4BDE95F2.1020506@suse.cz> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/03/2010 12:22 PM, Jiri Slaby wrote: > On 05/03/2010 11:18 AM, Avi Kivity wrote: > >> On 05/03/2010 12:03 PM, Jiri Slaby wrote: >> >>>>> Because vmalloc is used to allocate virtually contiguous memory. v in >>>>> vmalloc means virtually. >>>>> >>>>> >>>>> >>>>> >>>> A kmalloc()ed page is virtually contiguous, satisfying your requirement. >>>> >>>> >>> But it won't work well for vmalloc_to_{page,pfn} and similar. >>> >> Modify vmalloc_to_{page,pfn} accordingly. >> > When you get a slub in the middle of page, how? > Er, right. So a separate API is needed for users who are interested in memory, not pages. >>> Some code >>> may expect vmalloc result to be in the vmalloc area and page-aligned >>> (both in position and size). >>> >>> >> Both would be a bug IMO. vmalloc() follows kmalloc() and malloc() which >> only guarantee natural alignment. >> > Nope, from what I understand, vmalloc aligns (uses page allocator). Even > for purposes of vmalloc_to_*. > Correct, my mistake. -- error compiling committee.c: too many arguments to function