[<prev] [next>] [day] [month] [year] [list]
Message-ID: <34e1ae46cec25811cc821f0d9ee2b9e382d1c42e.camel@fb.com>
Date: Fri, 15 Apr 2022 18:06:22 +0000
From: Rik van Riel <riel@...com>
To: "linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"song@...nel.org" <song@...nel.org>,
"bpf@...r.kernel.org" <bpf@...r.kernel.org>
CC: "rick.p.edgecombe@...el.com" <rick.p.edgecombe@...el.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"daniel@...earbox.net" <daniel@...earbox.net>,
"hch@...radead.org" <hch@...radead.org>,
"mcgrof@...nel.org" <mcgrof@...nel.org>,
"ast@...nel.org" <ast@...nel.org>,
Kernel Team <Kernel-team@...com>,
"imbrenda@...ux.ibm.com" <imbrenda@...ux.ibm.com>
Subject: Re: [PATCH v4 bpf 3/4] module: introduce module_alloc_huge
On Fri, 2022-04-15 at 09:44 -0700, Song Liu wrote:
> Introduce module_alloc_huge, which allocates huge page backed memory
> in
> module memory space. The primary user of this memory is bpf_prog_pack
> (multiple BPF programs sharing a huge page).
>
> Signed-off-by: Song Liu <song@...nel.org>
Looks like the BPF might end up being the only user.
On my system I don't see one single kernel module that is
large enough to use an entire hugepage.
Oh well, it's a simple enough interface...
Reviewed-by: Rik van Riel <riel@...riel.com>
Powered by blists - more mailing lists