From: patchwork-bot+netdevbpf@kernel.org
To: Hou Tao <houtao@huaweicloud.com>
Cc: bpf@vger.kernel.org, linux-mm@kvack.org, martin.lau@linux.dev,
alexei.starovoitov@gmail.com, andrii@kernel.org, song@kernel.org,
haoluo@google.com, yonghong.song@linux.dev, daniel@iogearbox.net,
kpsingh@kernel.org, sdf@google.com, jolsa@kernel.org,
john.fastabend@gmail.com, houtao1@huawei.com, dennis@kernel.org,
tj@kernel.org, cl@linux.com, akpm@linux-foundation.org
Subject: Re: [PATCH bpf-next v3 0/7] bpf: Fixes for per-cpu kptr
Date: Fri, 20 Oct 2023 17:30:25 +0000 [thread overview]
Message-ID: <169782302501.9988.4889931337296268116.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231020133202.4043247-1-houtao@huaweicloud.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 20 Oct 2023 21:31:55 +0800 you wrote:
> From: Hou Tao <houtao1@huawei.com>
>
> Hi,
>
> The patchset aims to fix the problems found in the review of per-cpu
> kptr patch-set [0]. Patch #1 moves pcpu_lock after the invocation of
> pcpu_chunk_addr_search() and it is a micro-optimization for
> free_percpu(). The reason includes it in the patch is that the same
> logic is used in newly-added API pcpu_alloc_size(). Patch #2 introduces
> pcpu_alloc_size() for dynamic per-cpu area. Patch #2 and #3 use
> pcpu_alloc_size() to check whether or not unit_size matches with the
> size of underlying per-cpu area and to select a matching bpf_mem_cache.
> Patch #4 fixes the freeing of per-cpu kptr when these kptrs are freed by
> map destruction. The last patch adds test cases for these problems.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/7] mm/percpu.c: don't acquire pcpu_lock for pcpu_chunk_addr_search()
https://git.kernel.org/bpf/bpf-next/c/394e6869f018
- [bpf-next,v3,2/7] mm/percpu.c: introduce pcpu_alloc_size()
https://git.kernel.org/bpf/bpf-next/c/5897c912a66b
- [bpf-next,v3,3/7] bpf: Re-enable unit_size checking for global per-cpu allocator
https://git.kernel.org/bpf/bpf-next/c/fd496368ab75
- [bpf-next,v3,4/7] bpf: Use pcpu_alloc_size() in bpf_mem_free{_rcu}()
https://git.kernel.org/bpf/bpf-next/c/f6bbb0c00203
- [bpf-next,v3,5/7] bpf: Move the declaration of __bpf_obj_drop_impl() to bpf.h
https://git.kernel.org/bpf/bpf-next/c/c999470ea070
- [bpf-next,v3,6/7] bpf: Use bpf_global_percpu_ma for per-cpu kptr in __bpf_obj_drop_impl()
https://git.kernel.org/bpf/bpf-next/c/710701945f97
- [bpf-next,v3,7/7] selftests/bpf: Add more test cases for bpf memory allocator
https://git.kernel.org/bpf/bpf-next/c/30c44ceada16
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:[~2023-10-20 17:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 13:31 [PATCH bpf-next v3 0/7] bpf: Fixes for per-cpu kptr Hou Tao
2023-10-20 13:31 ` [PATCH bpf-next v3 1/7] mm/percpu.c: don't acquire pcpu_lock for pcpu_chunk_addr_search() Hou Tao
2023-10-20 13:31 ` [PATCH bpf-next v3 2/7] mm/percpu.c: introduce pcpu_alloc_size() Hou Tao
2023-10-20 17:48 ` Dennis Zhou
2023-10-20 17:58 ` Alexei Starovoitov
2023-10-20 18:03 ` Dennis Zhou
2023-10-20 21:17 ` Alexei Starovoitov
2023-10-21 1:20 ` Hou Tao
2023-10-21 2:03 ` Tejun Heo
2023-10-20 13:31 ` [PATCH bpf-next v3 3/7] bpf: Re-enable unit_size checking for global per-cpu allocator Hou Tao
2023-10-20 13:31 ` [PATCH bpf-next v3 4/7] bpf: Use pcpu_alloc_size() in bpf_mem_free{_rcu}() Hou Tao
2023-10-20 13:32 ` [PATCH bpf-next v3 5/7] bpf: Move the declaration of __bpf_obj_drop_impl() to bpf.h Hou Tao
2023-10-20 13:32 ` [PATCH bpf-next v3 6/7] bpf: Use bpf_global_percpu_ma for per-cpu kptr in __bpf_obj_drop_impl() Hou Tao
2023-10-20 13:32 ` [PATCH bpf-next v3 7/7] selftests/bpf: Add more test cases for bpf memory allocator Hou Tao
2023-10-20 17:30 ` 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=169782302501.9988.4889931337296268116.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cl@linux.com \
--cc=daniel@iogearbox.net \
--cc=dennis@kernel.org \
--cc=haoluo@google.com \
--cc=houtao1@huawei.com \
--cc=houtao@huaweicloud.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-mm@kvack.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=tj@kernel.org \
--cc=yonghong.song@linux.dev \
/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