From: patchwork-bot+netdevbpf@kernel.org
To: Yan Zhai <yan@cloudflare.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
john.fastabend@gmail.com, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org, mykolal@fb.com,
shuah@kernel.org, brianvv@google.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
kernel-team@cloudflare.com, houtao@huaweicloud.com
Subject: Re: [PATCH v3 bpf 0/2] bpf: skip non exist keys in generic_map_lookup_batch
Date: Wed, 19 Feb 2025 01:40:32 +0000 [thread overview]
Message-ID: <173992923201.98087.10855762431625409310.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1739171594.git.yan@cloudflare.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sun, 9 Feb 2025 23:22:31 -0800 you wrote:
> The generic_map_lookup_batch currently returns EINTR if it fails with
> ENOENT and retries several times on bpf_map_copy_value. The next batch
> would start from the same location, presuming it's a transient issue.
> This is incorrect if a map can actually have "holes", i.e.
> "get_next_key" can return a key that does not point to a valid value. At
> least the array of maps type may contain such holes legitly. Right now
> these holes show up, generic batch lookup cannot proceed any more. It
> will always fail with EINTR errors.
>
> [...]
Here is the summary with links:
- [v3,bpf,1/2] bpf: skip non exist keys in generic_map_lookup_batch
https://git.kernel.org/bpf/bpf/c/5644c6b50ffe
- [v3,bpf,2/2] selftests: bpf: test batch lookup on array of maps with holes
https://git.kernel.org/bpf/bpf/c/d66b7739176d
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:[~2025-02-19 1:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 7:22 [PATCH v3 bpf 0/2] bpf: skip non exist keys in generic_map_lookup_batch Yan Zhai
2025-02-10 7:22 ` [PATCH v3 bpf 1/2] " Yan Zhai
2025-02-10 9:19 ` Jiri Olsa
2025-02-10 14:47 ` Brian Vazquez
2025-02-10 16:21 ` Yan Zhai
2025-02-12 17:04 ` Jiri Olsa
2025-02-10 7:22 ` [PATCH v3 bpf 2/2] selftests: bpf: test batch lookup on array of maps with holes Yan Zhai
2025-02-19 1: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=173992923201.98087.10855762431625409310.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=brianvv@google.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=houtao@huaweicloud.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kernel-team@cloudflare.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yan@cloudflare.com \
--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