All of lore.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, kernel-team@fb.com, song@kernel.org,
	joannelkoong@gmail.com
Subject: Re: [PATCH bpf-next v8 0/5] bpf_loop inlining
Date: Tue, 21 Jun 2022 00:50:13 +0000	[thread overview]
Message-ID: <165577261377.6414.17748447759450199467.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220620235344.569325-1-eddyz87@gmail.com>

Hello:

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

On Tue, 21 Jun 2022 02:53:39 +0300 you wrote:
> Hi Everyone,
> 
> This is the next iteration of the patch. It includes changes suggested
> by Song, Joanne and Alexei. Please find updated intro message and
> change log below.
> 
> This patch implements inlining of calls to bpf_loop helper function
> when bpf_loop's callback is statically known. E.g. the rewrite does
> the following transformation during BPF program processing:
> 
> [...]

Here is the summary with links:
  - [bpf-next,v8,1/5] selftests/bpf: specify expected instructions in test_verifier tests
    https://git.kernel.org/bpf/bpf-next/c/933ff53191eb
  - [bpf-next,v8,2/5] selftests/bpf: allow BTF specs and func infos in test_verifier tests
    https://git.kernel.org/bpf/bpf-next/c/7a42008ca5c7
  - [bpf-next,v8,3/5] bpf: Inline calls to bpf_loop when callback is known
    https://git.kernel.org/bpf/bpf-next/c/1ade23711971
  - [bpf-next,v8,4/5] selftests/bpf: BPF test_verifier selftests for bpf_loop inlining
    https://git.kernel.org/bpf/bpf-next/c/f8acfdd04410
  - [bpf-next,v8,5/5] selftests/bpf: BPF test_prog selftests for bpf_loop inlining
    https://git.kernel.org/bpf/bpf-next/c/0e1bf9ed2000

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



      parent reply	other threads:[~2022-06-21  0:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20 23:53 [PATCH bpf-next v8 0/5] bpf_loop inlining Eduard Zingerman
2022-06-20 23:53 ` [PATCH bpf-next v8 1/5] selftests/bpf: specify expected instructions in test_verifier tests Eduard Zingerman
2022-06-20 23:53 ` [PATCH bpf-next v8 2/5] selftests/bpf: allow BTF specs and func infos " Eduard Zingerman
2022-06-20 23:53 ` [PATCH bpf-next v8 3/5] bpf: Inline calls to bpf_loop when callback is known Eduard Zingerman
2022-06-21  0:35   ` Song Liu
2022-06-20 23:53 ` [PATCH bpf-next v8 4/5] selftests/bpf: BPF test_verifier selftests for bpf_loop inlining Eduard Zingerman
2022-06-21  0:36   ` Song Liu
2022-06-20 23:53 ` [PATCH bpf-next v8 5/5] selftests/bpf: BPF test_prog " Eduard Zingerman
2022-06-21  0: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=165577261377.6414.17748447759450199467.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=eddyz87@gmail.com \
    --cc=joannelkoong@gmail.com \
    --cc=kernel-team@fb.com \
    --cc=song@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 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.