[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200414130203.GA20867@infradead.org>
Date: Tue, 14 Apr 2020 06:02:03 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Nicholas Piggin <npiggin@...il.com>
Cc: Christoph Hellwig <hch@...radead.org>,
Borislav Petkov <bp@...en8.de>,
Catalin Marinas <catalin.marinas@....com>,
"H. Peter Anvin" <hpa@...or.com>, linux-arch@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, linuxppc-dev@...ts.ozlabs.org,
Ingo Molnar <mingo@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Will Deacon <will@...nel.org>, x86@...nel.org
Subject: Re: [PATCH v2 4/4] mm/vmalloc: Hugepage vmalloc mappings
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?
Powered by blists - more mailing lists