From: patchwork-bot+netdevbpf@kernel.org
To: Feng zhou <zhoufeng.zf@bytedance.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org,
netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, duanxiongchun@bytedance.com,
songmuchun@bytedance.com, wangdongdong.6@bytedance.com,
cong.wang@bytedance.com, zhouchengming@bytedance.com
Subject: Re: [PATCH v6 0/2] Optimize performance of update hash-map when free is zero
Date: Sat, 11 Jun 2022 21:40:13 +0000 [thread overview]
Message-ID: <165498361355.20267.7962671859794283090.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220610023308.93798-1-zhoufeng.zf@bytedance.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 10 Jun 2022 10:33:06 +0800 you wrote:
> From: Feng Zhou <zhoufeng.zf@bytedance.com>
>
> We encountered bad case on big system with 96 CPUs that
> alloc_htab_elem() would last for 1ms. The reason is that after the
> prealloc hashtab has no free elems, when trying to update, it will still
> grab spin_locks of all cpus. If there are multiple update users, the
> competition is very serious.
>
> [...]
Here is the summary with links:
- [v6,1/2] bpf: avoid grabbing spin_locks of all cpus when no free elems
https://git.kernel.org/bpf/bpf-next/c/54a9c3a42d92
- [v6,2/2] selftest/bpf/benchs: Add bpf_map benchmark
https://git.kernel.org/bpf/bpf-next/c/89eda98428ce
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-06-11 21:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 2:33 [PATCH v6 0/2] Optimize performance of update hash-map when free is zero Feng zhou
2022-06-10 2:33 ` [PATCH v6 1/2] bpf: avoid grabbing spin_locks of all cpus when no free elems Feng zhou
2022-06-10 2:33 ` [PATCH v6 2/2] selftest/bpf/benchs: Add bpf_map benchmark Feng zhou
2022-06-11 21:40 ` 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=165498361355.20267.7962671859794283090.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=cong.wang@bytedance.com \
--cc=daniel@iogearbox.net \
--cc=duanxiongchun@bytedance.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=songmuchun@bytedance.com \
--cc=wangdongdong.6@bytedance.com \
--cc=yhs@fb.com \
--cc=zhouchengming@bytedance.com \
--cc=zhoufeng.zf@bytedance.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