From: patchwork-bot+netdevbpf@kernel.org
To: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@meta.com, eddyz87@gmail.com,
yatsenko@meta.com
Subject: Re: [PATCH bpf-next] bpf: Specialize inlined lookups for more htab types
Date: Thu, 05 Nov 2026 23:10:05 +0000 [thread overview]
Message-ID: <179392020599.229163.7828613010978206008.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261105-b4-hashtab-fast-hashfn-all-types-v1-1-287199376359@meta.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Thu, 05 Nov 2026 08:56:04 -0800 you wrote:
> From: Mykyta Yatsenko <yatsenko@meta.com>
>
> Commit 63b13537e6b2 ("bpf: Speed up htab lookups for u32/u64 keys")
> specializes the inlined lookup only for BPF_MAP_TYPE_HASH. LRU_HASH,
> PERCPU_HASH and HASH_OF_MAPS still call the generic lookup.
>
> Select the lookup function in all htab map_gen_lookup() callbacks by
> key size and by has_hash. has_hash does not change after map creation,
> so each variant uses a constant elem_has_hash. This also removes the
> load and the branch on htab->has_hash for other key sizes.
> LRU_PERCPU_HASH has no inlined lookup and does not change.
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: Specialize inlined lookups for more htab types
https://git.kernel.org/bpf/bpf-next/c/d03b6e1357dc
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:[~2026-11-05 23:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 16:56 [PATCH bpf-next] bpf: Specialize inlined lookups for more htab types Mykyta Yatsenko
2026-11-05 23:10 ` 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=179392020599.229163.7828613010978206008.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=eddyz87@gmail.com \
--cc=kernel-team@meta.com \
--cc=mykyta.yatsenko5@gmail.com \
--cc=yatsenko@meta.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