From: patchwork-bot+netdevbpf@kernel.org
To: Hou Tao <houtao@huaweicloud.com>
Cc: bpf@vger.kernel.org, martin.lau@linux.dev, andrii@kernel.org,
song@kernel.org, haoluo@google.com, yhs@fb.com, ast@kernel.org,
daniel@iogearbox.net, kpsingh@kernel.org, sdf@google.com,
jolsa@kernel.org, john.fastabend@gmail.com, paulmck@kernel.org,
rcu@vger.kernel.org, houtao1@huawei.com
Subject: Re: [PATCH bpf-next v2 0/2] Misc optimizations for bpf mem allocator
Date: Fri, 09 Dec 2022 02:00:15 +0000 [thread overview]
Message-ID: <167055121590.16670.16541321948945881937.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221209010947.3130477-1-houtao@huaweicloud.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 9 Dec 2022 09:09:45 +0800 you wrote:
> From: Hou Tao <houtao1@huawei.com>
>
> Hi,
>
> The patchset is just misc optimizations for bpf mem allocator. Patch 1
> fixes the OOM problem found during running hash-table update benchmark
> from qp-trie patchset [0]. The benchmark will add htab elements in
> batch and then delete elements in batch, so freed objects will stack on
> free_by_rcu and wait for the expiration of RCU grace period. There can
> be tens of thousands of freed objects and these objects are not
> available for new allocation, so adding htab element will continue to do
> new allocation.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] bpf: Reuse freed element in free_by_rcu during allocation
https://git.kernel.org/bpf/bpf-next/c/0893d6007db5
- [bpf-next,v2,2/2] bpf: Skip rcu_barrier() if rcu_trace_implies_rcu_gp() is true
https://git.kernel.org/bpf/bpf-next/c/822ed78fab13
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-12-09 2:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 1:09 [PATCH bpf-next v2 0/2] Misc optimizations for bpf mem allocator Hou Tao
2022-12-09 1:09 ` [PATCH bpf-next v2 1/2] bpf: Reuse freed element in free_by_rcu during allocation Hou Tao
2022-12-09 1:09 ` [PATCH bpf-next v2 2/2] bpf: Skip rcu_barrier() if rcu_trace_implies_rcu_gp() is true Hou Tao
2022-12-09 2:00 ` 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=167055121590.16670.16541321948945881937.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--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=martin.lau@linux.dev \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yhs@fb.com \
/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