public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, martin.lau@linux.dev, kernel-team@fb.com,
	yhs@fb.com, ecree.xilinx@gmail.com
Subject: Re: [PATCH bpf-next v4 0/1]  docs/bpf: Add description of register liveness tracking algorithm
Date: Fri, 03 Feb 2023 04:30:18 +0000	[thread overview]
Message-ID: <167539861801.7452.3340263117512202525.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230202125713.821931-1-eddyz87@gmail.com>

Hello:

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

On Thu,  2 Feb 2023 14:57:12 +0200 you wrote:
> An overview of the register tracking liveness algorithm.
> Previous versions posted here: [1], [2], [3].
> - Changes from RFC to v2 (suggested by Andrii Nakryiko):
>   - wording corrected to use term "stack slot" instead of "stack spill";
>   - parentage chain diagram updated to show nil links for frame #1;
>   - added example for non-BPF_DW writes behavior;
>   - explanation in "Read marks propagation for cache hits" is reworked.
> - Changes from v2 to v3:
>   - lot's of grammatical / wording fixes as suggested by David Vernet;
>   - "Register parentage chains" section is fixed to reflect what
>     happens to r1-r5 when function call is processed (as suggested by David and Alexei);
>   - Example in "Liveness marks tracking" section updated to explain
>     why partial writes should not lead to REG_LIVE_WRITTEN marks
>     (suggested by David);
>   - "Read marks propagation for cache hits" section updates:
>     - Explanation updated to hint why read marks should be propagated
>       before jumping to example (suggested by David);
>     - Removed box around B/D in the diagram updated (suggested by Alexei).
> - Changes from v3 to v4 (suggested by Edward Cree):
>   - register parentage chain diagram updated to explain why r6 mark is
>     not propagated;
>   - read mark propagation algorithm pseudo-code fixed to correctly
>     show "if state->live & REG_LIVE_WRITTEN" stop condition;
>   - general wording improvements in section "Liveness marks tracking".
> 
> [...]

Here is the summary with links:
  - [bpf-next,v4,1/1] docs/bpf: Add description of register liveness tracking algorithm
    https://git.kernel.org/bpf/bpf-next/c/cb6018485cd9

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



      parent reply	other threads:[~2023-02-03  4:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-02 12:57 [PATCH bpf-next v4 0/1] docs/bpf: Add description of register liveness tracking algorithm Eduard Zingerman
2023-02-02 12:57 ` [PATCH bpf-next v4 1/1] " Eduard Zingerman
2023-02-02 14:11   ` Edward Cree
2023-02-03  4:30 ` 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=167539861801.7452.3340263117512202525.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=ecree.xilinx@gmail.com \
    --cc=eddyz87@gmail.com \
    --cc=kernel-team@fb.com \
    --cc=martin.lau@linux.dev \
    --cc=yhs@fb.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