From: Christoph Hellwig <hch@infradead.org>
To: Song Liu <song@kernel.org>
Cc: bpf@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org,
akpm@linux-foundation.org, rick.p.edgecombe@intel.com,
hch@infradead.org, imbrenda@linux.ibm.com, mcgrof@kernel.org
Subject: Re: [PATCH v2 bpf 2/3] module: introduce module_alloc_huge
Date: Mon, 11 Apr 2022 21:20:05 -0700 [thread overview]
Message-ID: <YlT99YrkJyLVMdNH@infradead.org> (raw)
In-Reply-To: <20220411233549.740157-3-song@kernel.org>
On Mon, Apr 11, 2022 at 04:35:47PM -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).
I kow I lead you downthis road first, but I wonder if we just want to
pass a flag to module_alloc instead. This avoids duplicating all the
arch overrides.
next prev parent reply other threads:[~2022-04-12 4:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220411233549.740157-1-song@kernel.org>
[not found] ` <20220411233549.740157-4-song@kernel.org>
2022-04-11 23:52 ` [PATCH v2 bpf 3/3] bpf: use module_alloc_huge for bpf_prog_pack Song Liu
[not found] ` <20220411233549.740157-2-song@kernel.org>
2022-04-12 4:18 ` [PATCH v2 bpf 1/3] vmalloc: replace VM_NO_HUGE_VMAP with VM_ALLOW_HUGE_VMAP Christoph Hellwig
2022-04-12 6:00 ` Song Liu
2022-04-21 2:24 ` Nicholas Piggin
2022-04-21 3:35 ` Nicholas Piggin
[not found] ` <20220411233549.740157-3-song@kernel.org>
2022-04-12 4:20 ` Christoph Hellwig [this message]
2022-04-12 6:11 ` [PATCH v2 bpf 2/3] module: introduce module_alloc_huge Song Liu
[not found] ` <20220411233549.740157-5-song@kernel.org>
2022-04-12 4:20 ` [PATCH v2 bpf 3/3] bpf: use vmalloc with VM_ALLOW_HUGE_VMAP for bpf_prog_pack Christoph Hellwig
2022-04-12 6:12 ` Song Liu
2022-04-12 17:20 ` Edgecombe, Rick P
2022-04-12 21:00 ` Song Liu
2022-04-13 15:51 ` Edgecombe, Rick P
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YlT99YrkJyLVMdNH@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=imbrenda@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=rick.p.edgecombe@intel.com \
--cc=song@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).