[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1586875675.f8q1grbltc.astroid@bobo.none>
Date: Wed, 15 Apr 2020 00:48:13 +1000
From: Nicholas Piggin <npiggin@...il.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: 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
Excerpts from Christoph Hellwig's message of April 14, 2020 11:02 pm:
> 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?
Yes.
Thanks,
Nick
Powered by blists - more mailing lists