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,
memxor@gmail.com, yatsenko@meta.com, a.s.protopopov@gmail.com
Subject: Re: [PATCH bpf-next v3] bpf: Speed up htab lookups for u32/u64 keys
Date: Tue, 22 Sep 2026 19:20:12 +0000 [thread overview]
Message-ID: <179010481220.48438.10259992249871053986.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260922-hashtab_fast_hashfn-v3-1-b7b0e9bc33ac@meta.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 22 Sep 2026 10:58:02 -0700 you wrote:
> From: Mykyta Yatsenko <yatsenko@meta.com>
>
> Four- and eight-byte keys are common enough to warrant specialized htab
> lookups. Use jhash_1word() and jhash_2words() for these key sizes instead
> of the generic jhash2() path.
>
> For JITed BPF_MAP_TYPE_HASH lookups, htab_map_gen_lookup() also knows the
> map's fixed key size. Select u32- and u64-specific lookup entry points so
> the compiler can specialize both hashing and key comparison. Other key
> sizes continue to use the generic lookup entry point.
>
> [...]
Here is the summary with links:
- [bpf-next,v3] bpf: Speed up htab lookups for u32/u64 keys
https://git.kernel.org/bpf/bpf-next/c/63b13537e6b2
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-09-22 19:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 17:58 [PATCH bpf-next v3] bpf: Speed up htab lookups for u32/u64 keys Mykyta Yatsenko
2026-09-22 18:08 ` sashiko-bot
2026-09-22 18:10 ` Mykyta Yatsenko
2026-09-22 18:49 ` bot+bpf-ci
2026-09-22 19:20 ` 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=179010481220.48438.10259992249871053986.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=a.s.protopopov@gmail.com \
--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=memxor@gmail.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