From: Song Liu <song@kernel.org>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: bpf@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, x86@kernel.org, peterz@infradead.org,
hch@lst.de, rick.p.edgecombe@intel.com, rppt@kernel.org,
mcgrof@kernel.org
Subject: Re: [PATCH bpf-next v4 1/6] vmalloc: introduce execmem_alloc, execmem_free, and execmem_fill
Date: Mon, 28 Nov 2022 09:53:15 -0800 [thread overview]
Message-ID: <CAPhsuW71F6MzmU8hhd1NmZQ=-hAAxZh4ZEr5A6zPOpOgM925Nw@mail.gmail.com> (raw)
In-Reply-To: <882e2964-932e-0113-d3cd-344281add3a1@iogearbox.net>
On Mon, Nov 21, 2022 at 7:52 AM Daniel Borkmann <daniel@iogearbox.net> wrote:
[...]
> > + */
> > +void *execmem_alloc(unsigned long size, unsigned long align)
> > +{
> > + struct vmap_area *va, *tmp;
> > + unsigned long addr;
> > + enum fit_type type;
> > + int ret;
> > +
> > + va = kmem_cache_alloc_node(vmap_area_cachep, GFP_KERNEL, NUMA_NO_NODE);
> > + if (unlikely(!va))
> > + return NULL;
> > +
> > +again:
> > + preload_this_cpu_lock(&free_text_area_lock, GFP_KERNEL, NUMA_NO_NODE);
> > + tmp = find_vmap_lowest_match(&free_text_area_root, size, align, 1, false);
> > +
> > + if (!tmp) {
> > + unsigned long alloc_size;
> > + void *ptr;
> > +
> > + spin_unlock(&free_text_area_lock);
> > +
> > + /*
> > + * Not enough continuous space in free_text_area_root, try
> > + * allocate more memory. The memory is first added to
> > + * vmap_area_root, and then moved to free_text_area_root.
> > + */
> > + alloc_size = roundup(size, PMD_SIZE * num_online_nodes());
> > + ptr = __vmalloc_node_range(alloc_size, PMD_SIZE, EXEC_MEM_START,
> > + EXEC_MEM_END, GFP_KERNEL, PAGE_KERNEL,
> > + VM_ALLOW_HUGE_VMAP | VM_NO_GUARD,
> > + NUMA_NO_NODE, __builtin_return_address(0));
> > + if (unlikely(!ptr))
> > + goto err_out;
> > +
> > + move_vmap_to_free_text_tree(ptr);
> > + goto again;
> > + }
> > +
> > + addr = roundup(tmp->va_start, align);
> > + type = classify_va_fit_type(tmp, addr, size);
> > + if (WARN_ON_ONCE(type == NOTHING_FIT))
> > + goto err_out_unlock;
>
> Isn't this already covered in adjust_va_to_fit_type()?
That's right! Now we can get rid of err_out_unlock. Thanks!
Also fixed other nits.
Song
[...]
next prev parent reply other threads:[~2022-11-28 17:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 20:23 [PATCH bpf-next v4 0/6] execmem_alloc for BPF programs Song Liu
2022-11-17 20:23 ` [PATCH bpf-next v4 1/6] vmalloc: introduce execmem_alloc, execmem_free, and execmem_fill Song Liu
[not found] ` <882e2964-932e-0113-d3cd-344281add3a1@iogearbox.net>
2022-11-21 15:55 ` Christoph Hellwig
2022-11-21 16:29 ` Song Liu
2022-11-21 19:55 ` Luis Chamberlain
2022-11-22 2:55 ` Song Liu
2022-11-22 6:13 ` Christoph Hellwig
2022-11-22 17:25 ` Song Liu
2022-11-28 17:53 ` Song Liu [this message]
2022-11-17 20:23 ` [PATCH bpf-next v4 2/6] x86/alternative: support execmem_alloc() and execmem_free() Song Liu
2022-11-17 20:23 ` [PATCH bpf-next v4 3/6] selftests/vm: extend test_vmalloc to test execmem_* APIs Song Liu
2022-11-17 20:23 ` [PATCH bpf-next v4 4/6] bpf: use execmem_alloc for bpf program and bpf dispatcher Song Liu
2022-11-17 20:23 ` [PATCH bpf-next v4 5/6] vmalloc: introduce register_text_tail_vm() Song Liu
2022-11-17 20:23 ` [PATCH bpf-next v4 6/6] x86: use register_text_tail_vm Song Liu
2022-11-21 20:12 ` [PATCH bpf-next v4 0/6] execmem_alloc for BPF programs Luis Chamberlain
2022-11-21 20:20 ` Luis Chamberlain
2022-11-22 2:36 ` Song Liu
2022-12-08 2:48 ` Luis Chamberlain
2022-11-22 2:28 ` Song Liu
2022-11-23 0:21 ` Luis Chamberlain
2022-11-23 5:06 ` Song Liu
2022-11-30 9:53 ` Mike Rapoport
2022-11-30 9:41 ` Mike Rapoport
2022-11-22 2:55 ` Song Liu
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='CAPhsuW71F6MzmU8hhd1NmZQ=-hAAxZh4ZEr5A6zPOpOgM925Nw@mail.gmail.com' \
--to=song@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=hch@lst.de \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=rppt@kernel.org \
--cc=x86@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