From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH v2 4/4] mm/vmalloc: Hugepage vmalloc mappings Date: Tue, 14 Apr 2020 06:02:03 -0700 Message-ID: <20200414130203.GA20867@infradead.org> References: <20200413125303.423864-1-npiggin@gmail.com> <20200413125303.423864-5-npiggin@gmail.com> <20200414072316.GA5503@infradead.org> <1586864403.0qfilei2ft.astroid@bobo.none> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1586864403.0qfilei2ft.astroid@bobo.none> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane-mx.org@lists.infradead.org To: Nicholas Piggin Cc: linux-arch@vger.kernel.org, Will Deacon , Catalin Marinas , x86@kernel.org, linux-kernel@vger.kernel.org, Christoph Hellwig , linux-mm@kvack.org, Ingo Molnar , Borislav Petkov , "H. Peter Anvin" , Thomas Gleixner , linuxppc-dev@lists.ozlabs.org, linux-arm-kernel@lists.infradead.org List-Id: linux-arch.vger.kernel.org On Tue, Apr 14, 2020 at 10:13:44PM +1000, Nicholas Piggin wrote: > Which case? Usually the answer would be because you don't want to use > contiguous physical memory and/or you don't want to use the linear > mapping. But with huge pages you do by definition already use large contiguous areas. So you want allocations larger than "small" huge pages but not using gigantic pages using vmalloc? From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Tue, 14 Apr 2020 06:02:03 -0700 From: Christoph Hellwig Subject: Re: [PATCH v2 4/4] mm/vmalloc: Hugepage vmalloc mappings Message-ID: <20200414130203.GA20867@infradead.org> References: <20200413125303.423864-1-npiggin@gmail.com> <20200413125303.423864-5-npiggin@gmail.com> <20200414072316.GA5503@infradead.org> <1586864403.0qfilei2ft.astroid@bobo.none> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1586864403.0qfilei2ft.astroid@bobo.none> Sender: owner-linux-mm@kvack.org To: Nicholas Piggin Cc: Christoph Hellwig , Borislav Petkov , Catalin Marinas , "H. Peter Anvin" , linux-arch@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org, Ingo Molnar , Thomas Gleixner , Will Deacon , x86@kernel.org List-ID: Message-ID: <20200414130203.lym_oYhZrW1bldtxPW5nVb6bah3MSQT6NhRJIv5FiuU@z> On Tue, Apr 14, 2020 at 10:13:44PM +1000, Nicholas Piggin wrote: > Which case? Usually the answer would be because you don't want to use > contiguous physical memory and/or you don't want to use the linear > mapping. But with huge pages you do by definition already use large contiguous areas. So you want allocations larger than "small" huge pages but not using gigantic pages using vmalloc?