[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <87tubfm1wv.ffs@tglx>
Date: Thu, 31 Mar 2022 01:54:56 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Song Liu <song@...nel.org>, linux-mm@...ck.org,
bpf@...r.kernel.org, netdev@...r.kernel.org, x86@...nel.org
Cc: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
kernel-team@...com, akpm@...ux-foundation.org,
pmenzel@...gen.mpg.de, rick.p.edgecombe@...el.com,
Song Liu <song@...nel.org>
Subject: Re: [PATCH bpf 3/4] x86: select HAVE_ARCH_HUGE_VMALLOC_FLAG for X86_64
On Wed, Mar 30 2022 at 15:56, Song Liu wrote:
> As HAVE_ARCH_HUGE_VMALLOC is not ready for X86_64, enable
> HAVE_ARCH_HUGE_VMALLOC_FLAG to allow bpf_prog_pack to allocate huge
> pages.
Despite HAVE_ARCH_HUGE_VMALLOC being not ready for X86_64 enable it
nevertheless?
I assume you wanted to say something like this:
The shortcomings of huge vmalloc allocations have been fixed in the
memory management core code, so reenable HAVE_ARCH_HUGE_VMALLOC.
Thanks,
tglx
Powered by blists - more mailing lists