From: patchwork-bot+netdevbpf@kernel.org
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: davem@davemloft.net, daniel@iogearbox.net, andrii@kernel.org,
tj@kernel.org, memxor@gmail.com, delyank@fb.com,
linux-mm@kvack.org, bpf@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH v6 bpf-next 00/16] bpf: BPF specific memory allocator.
Date: Mon, 05 Sep 2022 13:50:18 +0000 [thread overview]
Message-ID: <166238581892.6349.8060523732700103598.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220902211058.60789-1-alexei.starovoitov@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Fri, 2 Sep 2022 14:10:42 -0700 you wrote:
> From: Alexei Starovoitov <ast@kernel.org>
>
> Introduce any context BPF specific memory allocator.
>
> Tracing BPF programs can attach to kprobe and fentry. Hence they
> run in unknown context where calling plain kmalloc() might not be safe.
> Front-end kmalloc() with per-cpu cache of free elements.
> Refill this cache asynchronously from irq_work.
>
> [...]
Here is the summary with links:
- [v6,bpf-next,01/16] bpf: Introduce any context BPF specific memory allocator.
https://git.kernel.org/bpf/bpf-next/c/7c8199e24fa0
- [v6,bpf-next,02/16] bpf: Convert hash map to bpf_mem_alloc.
https://git.kernel.org/bpf/bpf-next/c/fba1a1c6c912
- [v6,bpf-next,03/16] selftests/bpf: Improve test coverage of test_maps
https://git.kernel.org/bpf/bpf-next/c/37521bffdd2d
- [v6,bpf-next,04/16] samples/bpf: Reduce syscall overhead in map_perf_test.
https://git.kernel.org/bpf/bpf-next/c/89dc8d0c38e0
- [v6,bpf-next,05/16] bpf: Relax the requirement to use preallocated hash maps in tracing progs.
https://git.kernel.org/bpf/bpf-next/c/34dd3bad1a6f
- [v6,bpf-next,06/16] bpf: Optimize element count in non-preallocated hash map.
https://git.kernel.org/bpf/bpf-next/c/86fe28f7692d
- [v6,bpf-next,07/16] bpf: Optimize call_rcu in non-preallocated hash map.
https://git.kernel.org/bpf/bpf-next/c/0fd7c5d43339
- [v6,bpf-next,08/16] bpf: Adjust low/high watermarks in bpf_mem_cache
https://git.kernel.org/bpf/bpf-next/c/7c266178aa51
- [v6,bpf-next,09/16] bpf: Batch call_rcu callbacks instead of SLAB_TYPESAFE_BY_RCU.
https://git.kernel.org/bpf/bpf-next/c/8d5a8011b35d
- [v6,bpf-next,10/16] bpf: Add percpu allocation support to bpf_mem_alloc.
https://git.kernel.org/bpf/bpf-next/c/4ab67149f3c6
- [v6,bpf-next,11/16] bpf: Convert percpu hash map to per-cpu bpf_mem_alloc.
https://git.kernel.org/bpf/bpf-next/c/ee4ed53c5eb6
- [v6,bpf-next,12/16] bpf: Remove tracing program restriction on map types
https://git.kernel.org/bpf/bpf-next/c/96da3f7d489d
- [v6,bpf-next,13/16] bpf: Prepare bpf_mem_alloc to be used by sleepable bpf programs.
https://git.kernel.org/bpf/bpf-next/c/dccb4a9013a6
- [v6,bpf-next,14/16] bpf: Remove prealloc-only restriction for sleepable bpf programs.
https://git.kernel.org/bpf/bpf-next/c/02cc5aa29e8c
- [v6,bpf-next,15/16] bpf: Remove usage of kmem_cache from bpf_mem_cache.
https://git.kernel.org/bpf/bpf-next/c/bfc03c15bebf
- [v6,bpf-next,16/16] bpf: Optimize rcu_barrier usage between hash map and bpf_mem_alloc.
https://git.kernel.org/bpf/bpf-next/c/9f2c6e96c65e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-09-05 13:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 21:10 Alexei Starovoitov
2022-09-02 21:10 ` [PATCH v6 bpf-next 01/16] bpf: Introduce any context " Alexei Starovoitov
2022-09-02 21:10 ` [PATCH v6 bpf-next 02/16] bpf: Convert hash map to bpf_mem_alloc Alexei Starovoitov
2022-09-02 21:10 ` [PATCH v6 bpf-next 03/16] selftests/bpf: Improve test coverage of test_maps Alexei Starovoitov
2022-09-02 21:10 ` [PATCH v6 bpf-next 04/16] samples/bpf: Reduce syscall overhead in map_perf_test Alexei Starovoitov
2022-09-02 21:10 ` [PATCH v6 bpf-next 05/16] bpf: Relax the requirement to use preallocated hash maps in tracing progs Alexei Starovoitov
2022-09-02 21:10 ` [PATCH v6 bpf-next 06/16] bpf: Optimize element count in non-preallocated hash map Alexei Starovoitov
2022-09-02 21:10 ` [PATCH v6 bpf-next 07/16] bpf: Optimize call_rcu " Alexei Starovoitov
2022-09-02 21:10 ` [PATCH v6 bpf-next 08/16] bpf: Adjust low/high watermarks in bpf_mem_cache Alexei Starovoitov
2022-09-02 21:10 ` [PATCH v6 bpf-next 09/16] bpf: Batch call_rcu callbacks instead of SLAB_TYPESAFE_BY_RCU Alexei Starovoitov
2022-09-02 21:10 ` [PATCH v6 bpf-next 10/16] bpf: Add percpu allocation support to bpf_mem_alloc Alexei Starovoitov
2022-09-02 21:10 ` [PATCH v6 bpf-next 11/16] bpf: Convert percpu hash map to per-cpu bpf_mem_alloc Alexei Starovoitov
2022-09-02 21:10 ` [PATCH v6 bpf-next 12/16] bpf: Remove tracing program restriction on map types Alexei Starovoitov
2022-09-02 21:10 ` [PATCH v6 bpf-next 13/16] bpf: Prepare bpf_mem_alloc to be used by sleepable bpf programs Alexei Starovoitov
2022-09-02 21:10 ` [PATCH v6 bpf-next 14/16] bpf: Remove prealloc-only restriction for " Alexei Starovoitov
2022-09-02 21:10 ` [PATCH v6 bpf-next 15/16] bpf: Remove usage of kmem_cache from bpf_mem_cache Alexei Starovoitov
2022-09-02 21:10 ` [PATCH v6 bpf-next 16/16] bpf: Optimize rcu_barrier usage between hash map and bpf_mem_alloc Alexei Starovoitov
2022-09-05 13:50 ` patchwork-bot+netdevbpf [this message]
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=166238581892.6349.8060523732700103598.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=delyank@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-mm@kvack.org \
--cc=memxor@gmail.com \
--cc=tj@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