From: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>
To: sashiko-reviews@lists.linux.dev
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v3] bpf: Speed up htab lookups for u32/u64 keys
Date: Tue, 22 Sep 2026 19:10:50 +0100 [thread overview]
Message-ID: <be18926e-124c-40b1-9846-b99277c800ad@gmail.com> (raw)
In-Reply-To: <20260922180843.CB7721F000FF@smtp.kernel.org>
On 9/22/26 7:08 PM, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] bpf: missed u32/u64 lookup optimization for LRU/per-CPU/of_map variants
> --
>
> commit 88a648ce718a5816a7cc1175a104d2f26afc58c0
> Author: Mykyta Yatsenko <yatsenko@meta.com>
>
> bpf: Speed up htab lookups for u32/u64 keys
>
> This commit introduces specialized hashing and specific lookup entry points
> for 4-byte and 8-byte keys in BPF hash maps. It achieves significant
> throughput improvements for standard BPF_MAP_TYPE_HASH lookups.
>
>> diff --git a/kernel/bpf/hashtab.c b/kernel/bpf/hashtab.c
>> index 6f331c80130d7..f744a42bb8139 100644
>> --- a/kernel/bpf/hashtab.c
>> +++ b/kernel/bpf/hashtab.c
>
> [ ... ]
>
>> @@ -783,7 +805,16 @@ static int htab_map_gen_lookup(struct bpf_map *map, struct bpf_insn *insn_buf)
>>
>> BUILD_BUG_ON(!__same_type(&__htab_map_lookup_elem,
>> (void *(*)(struct bpf_map *map, void *key))NULL));
>> - *insn++ = BPF_EMIT_CALL(__htab_map_lookup_elem);
>> + BUILD_BUG_ON(!__same_type(&__htab_map_lookup_elem_u32,
>> + (void *(*)(struct bpf_map *map, void *key))NULL));
>> + BUILD_BUG_ON(!__same_type(&__htab_map_lookup_elem_u64,
>> + (void *(*)(struct bpf_map *map, void *key))NULL));
>> + if (map->key_size == sizeof(u32))
>> + *insn++ = BPF_EMIT_CALL(__htab_map_lookup_elem_u32);
>> + else if (map->key_size == sizeof(u64))
>> + *insn++ = BPF_EMIT_CALL(__htab_map_lookup_elem_u64);
>> + else
>> + *insn++ = BPF_EMIT_CALL(__htab_map_lookup_elem);
>
> [Severity: Medium]
> Does this miss an opportunity to apply the identical u32/u64 lookup
> optimization to the LRU, per-CPU, and hash-of-maps variants?
>
> It looks like specialized JIT lookup generators were added here for
> standard hash maps in htab_map_gen_lookup(), but identically structured
> functions in the same file such as htab_lru_map_gen_lookup(),
> htab_percpu_map_gen_lookup(), and htab_of_map_gen_lookup() still
> unconditionally emit a call to the unspecialized __htab_map_lookup_elem.
>
> Would it make sense to update those generators as well, so these heavily
> utilized map variants do not miss out on the same performance gains?
yes, I think this is a good idea.>
>> *insn++ = BPF_JMP_IMM(BPF_JEQ, ret, 0, 1);
>> *insn++ = BPF_ALU64_IMM(BPF_ADD, ret,
>> offsetof(struct htab_elem, key) +
>
next prev parent reply other threads:[~2026-09-22 18:10 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 [this message]
2026-09-22 18:49 ` bot+bpf-ci
2026-09-22 19:20 ` patchwork-bot+netdevbpf
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=be18926e-124c-40b1-9846-b99277c800ad@gmail.com \
--to=mykyta.yatsenko5@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=sashiko-reviews@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.