From: patchwork-bot+netdevbpf@kernel.org
To: David Verbeiren <david.verbeiren@tessares.net>
Cc: bpf@vger.kernel.org, andrii@kernel.org, netdev@vger.kernel.org,
matthieu.baerts@tessares.net
Subject: Re: [PATCH bpf v4] bpf: zero-fill re-used per-cpu map element
Date: Fri, 06 Nov 2020 04:10:04 +0000 [thread overview]
Message-ID: <160463580428.4516.12981335406471843015.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201104112332.15191-1-david.verbeiren@tessares.net>
Hello:
This patch was applied to bpf/bpf.git (refs/heads/master):
On Wed, 4 Nov 2020 12:23:32 +0100 you wrote:
> Zero-fill element values for all other cpus than current, just as
> when not using prealloc. This is the only way the bpf program can
> ensure known initial values for all cpus ('onallcpus' cannot be
> set when coming from the bpf program).
>
> The scenario is: bpf program inserts some elements in a per-cpu
> map, then deletes some (or userspace does). When later adding
> new elements using bpf_map_update_elem(), the bpf program can
> only set the value of the new elements for the current cpu.
> When prealloc is enabled, previously deleted elements are re-used.
> Without the fix, values for other cpus remain whatever they were
> when the re-used entry was previously freed.
>
> [...]
Here is the summary with links:
- [bpf,v4] bpf: zero-fill re-used per-cpu map element
https://git.kernel.org/bpf/bpf/c/d3bec0138bfb
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:[~2020-11-06 4:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 12:37 [PATCH bpf] bpf: zero-fill re-used per-cpu map element David Verbeiren
2020-10-26 22:47 ` Andrii Nakryiko
2020-10-27 14:48 ` David Verbeiren
2020-10-27 22:13 ` [PATCH bpf v2] " David Verbeiren
2020-10-27 22:55 ` Andrii Nakryiko
2020-10-29 14:44 ` David Verbeiren
2020-10-29 22:40 ` Andrii Nakryiko
2020-11-03 15:47 ` [PATCH bpf v3] " David Verbeiren
2020-11-03 18:19 ` Andrii Nakryiko
2020-11-04 11:23 ` [PATCH bpf v4] " David Verbeiren
2020-11-04 20:45 ` Andrii Nakryiko
2020-11-06 4: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=160463580428.4516.12981335406471843015.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=david.verbeiren@tessares.net \
--cc=matthieu.baerts@tessares.net \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).