From: patchwork-bot+netdevbpf@kernel.org
To: Hou Tao <houtao@huaweicloud.com>
Cc: bpf@vger.kernel.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, aspsk@isovalent.com,
houtao1@huawei.com
Subject: Re: [PATCH bpf-next 0/3] selftests/bpf: Fixes for map_percpu_stats test
Date: Thu, 02 Nov 2023 16:50:25 +0000 [thread overview]
Message-ID: <169894382510.17546.8408450524155416380.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231101032455.3808547-1-houtao@huaweicloud.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 1 Nov 2023 11:24:52 +0800 you wrote:
> From: Hou Tao <houtao1@huawei.com>
>
> Hi,
>
> BPF CI failed due to map_percpu_stats_percpu_hash from time to time [1].
> It seems that the failure reason is per-cpu bpf memory allocator may not
> be able to allocate per-cpu pointer successfully and it can not refill
> free llist timely, and bpf_map_update_elem() will return -ENOMEM.
>
> [...]
Here is the summary with links:
- [bpf-next,1/3] selftests/bpf: Use value with enough-size when updating per-cpu map
https://git.kernel.org/bpf/bpf-next/c/3f1f234e677b
- [bpf-next,2/3] selftests/bpf: Export map_update_retriable()
https://git.kernel.org/bpf/bpf-next/c/ff38534e8251
- [bpf-next,3/3] selftsets/bpf: Retry map update for non-preallocated per-cpu map
https://git.kernel.org/bpf/bpf-next/c/57688b2a543b
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-11-02 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 3:24 [PATCH bpf-next 0/3] selftests/bpf: Fixes for map_percpu_stats test Hou Tao
2023-11-01 3:24 ` [PATCH bpf-next 1/3] selftests/bpf: Use value with enough-size when updating per-cpu map Hou Tao
2023-11-01 3:24 ` [PATCH bpf-next 2/3] selftests/bpf: Export map_update_retriable() Hou Tao
2023-11-01 3:24 ` [PATCH bpf-next 3/3] selftsets/bpf: Retry map update for non-preallocated per-cpu map Hou Tao
2023-11-02 16: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=169894382510.17546.8408450524155416380.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=aspsk@isovalent.com \
--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=sdf@google.com \
--cc=song@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