From: patchwork-bot+netdevbpf@kernel.org
To: Qiliang Yuan <realwujing@gmail.com>
Cc: alexei.starovoitov@gmail.com, eddyz87@gmail.com,
andrii.nakryiko@gmail.com, andrii@kernel.org, ast@kernel.org,
bpf@vger.kernel.org, daniel@iogearbox.net, haoluo@google.com,
jolsa@kernel.org, kpsingh@kernel.org,
linux-kernel@vger.kernel.org, martin.lau@linux.dev,
sdf@fomichev.me, song@kernel.org, yonghong.song@linux.dev
Subject: Re: [PATCH v4] bpf/verifier: optimize ID mapping reset in states_equal
Date: Tue, 20 Jan 2026 19:40:07 +0000 [thread overview]
Message-ID: <176893800760.583014.3550645133045023335.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260120023234.77673-1-realwujing@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Tue, 20 Jan 2026 10:32:34 +0800 you wrote:
> Currently, reset_idmap_scratch() performs a 4.7KB memset() in every
> states_equal() call. Optimize this by using a counter to track used
> ID mappings, replacing the O(N) memset() with an O(1) reset and
> bounding the search loop in check_ids().
>
> Acked-by: Eduard Zingerman <eddyz87@gmail.com>
> Signed-off-by: Qiliang Yuan <realwujing@gmail.com>
>
> [...]
Here is the summary with links:
- [v4] bpf/verifier: optimize ID mapping reset in states_equal
https://git.kernel.org/bpf/bpf-next/c/f81c07a6e98e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-01-20 19:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 14:49 [PATCH] bpf/verifier: optimize ID mapping reset in states_equal wujing
2026-01-15 20:36 ` Eduard Zingerman
2026-01-15 22:19 ` Andrii Nakryiko
2026-01-16 9:08 ` [PATCH v2] " Qiliang Yuan
2026-01-19 19:42 ` Eduard Zingerman
2026-01-20 1:56 ` [PATCH v3] " Qiliang Yuan
2026-01-20 2:09 ` Alexei Starovoitov
2026-01-20 2:32 ` [PATCH v4] " Qiliang Yuan
2026-01-20 19:40 ` patchwork-bot+netdevbpf [this message]
2026-01-16 9:29 ` [PATCH v2] " Qiliang Yuan
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=176893800760.583014.3550645133045023335.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=realwujing@gmail.com \
--cc=sdf@fomichev.me \
--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