BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ritesh Oedayrajsingh Varma <ritesh@superluminal.eu>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	john.fastabend@gmail.com, andrii@kernel.org,
	houtao@huaweicloud.com, jelle@superluminal.eu
Subject: Re: [PATCH bpf-next] bpf: optimize bpf_map_update_elem() for map-in-map types
Date: Sat, 29 Nov 2025 17:50:30 +0000	[thread overview]
Message-ID: <176443863006.1061209.10606164337894467600.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251128000422.20462-1-ritesh@superluminal.eu>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Fri, 28 Nov 2025 01:02:35 +0100 you wrote:
> Updating a BPF_MAP_TYPE_HASH_OF_MAPS or BPF_MAP_TYPE_ARRAY_OF_MAPS via
> bpf_map_update_elem() is very expensive.
> 
> In one of our workloads, we're inserting ~1400 maps of type
> BPF_MAP_TYPE_ARRAY into a BPF_MAP_TYPE_ARRAY_OF_MAPS. This takes ~21
> seconds on a single thread, with an average of ~15ms per call:
> 
> [...]

Here is the summary with links:
  - [bpf-next] bpf: optimize bpf_map_update_elem() for map-in-map types
    https://git.kernel.org/bpf/bpf-next/c/ff34657aa72a

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2025-11-29 17:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-28  0:02 [PATCH bpf-next] bpf: optimize bpf_map_update_elem() for map-in-map types Ritesh Oedayrajsingh Varma
2025-11-29 17:50 ` 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=176443863006.1061209.10606164337894467600.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=houtao@huaweicloud.com \
    --cc=jelle@superluminal.eu \
    --cc=john.fastabend@gmail.com \
    --cc=ritesh@superluminal.eu \
    /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