From: Yonghong Song <yonghong.song@linux.dev>
To: Daniel Borkmann <daniel@iogearbox.net>, bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
kernel-team@fb.com, Martin KaFai Lau <martin.lau@kernel.org>
Subject: Re: [PATCH bpf-next v2 2/3] bpf: Remove 'may_goto 0' instruction in opt_remove_nops()
Date: Mon, 20 Jan 2025 19:20:27 -0800 [thread overview]
Message-ID: <4e621ff0-c40f-44ed-9610-8eadfd9f3cf1@linux.dev> (raw)
In-Reply-To: <0056055b-338a-49f1-b6bf-fa11440cb959@iogearbox.net>
On 1/20/25 7:29 AM, Daniel Borkmann wrote:
> On 1/18/25 8:20 PM, Yonghong Song wrote:
>> Since 'may_goto 0' insns are actually no-op, let us remove them.
>> Otherwise, verifier will generate code like
>> /* r10 - 8 stores the implicit loop count */
>> r11 = *(u64 *)(r10 -8)
>> if r11 == 0x0 goto pc+2
>> r11 -= 1
>> *(u64 *)(r10 -8) = r11
>>
>> which is the pure overhead.
>>
>> The following code patterns (from the previous commit) are also
>> handled:
>> may_goto 2
>> may_goto 1
>> may_goto 0
>>
>> With this commit, the above three 'may_goto' insns are all
>> eliminated.
>>
>> Signed-off-by: Yonghong Song <yonghong.song@linux.dev>
>> ---
>> kernel/bpf/verifier.c | 9 +++++++--
>> 1 file changed, 7 insertions(+), 2 deletions(-)
>>
>> diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
>> index 963dfda81c06..784547aa40a8 100644
>> --- a/kernel/bpf/verifier.c
>> +++ b/kernel/bpf/verifier.c
>> @@ -20187,20 +20187,25 @@ static const struct bpf_insn NOP =
>> BPF_JMP_IMM(BPF_JA, 0, 0, 0);
>> static int opt_remove_nops(struct bpf_verifier_env *env)
>> {
>> + const struct bpf_insn may_goto_0 = BPF_RAW_INSN(BPF_JMP |
>> BPF_JCOND, 0, 0, 0, 0);
>> const struct bpf_insn ja = NOP;
>> struct bpf_insn *insn = env->prog->insnsi;
>> int insn_cnt = env->prog->len;
>> + bool is_may_goto_0, is_ja;
>> int i, err;
>> for (i = 0; i < insn_cnt; i++) {
>> - if (memcmp(&insn[i], &ja, sizeof(ja)))
>> + is_may_goto_0 = !memcmp(&insn[i], &may_goto_0,
>> sizeof(may_goto_0));
>> + is_ja = !memcmp(&insn[i], &ja, sizeof(ja));
>> +
>> + if (!is_may_goto_0 && !is_ja)
>> continue;
>
> Why the extra may_goto_0 stack var?
>
> diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
> index 245f1f3f1aec..16ba26295ec7 100644
> --- a/kernel/bpf/verifier.c
> +++ b/kernel/bpf/verifier.c
> @@ -20185,16 +20185,19 @@ static int opt_remove_dead_code(struct
> bpf_verifier_env *env)
> }
>
> static const struct bpf_insn NOP = BPF_JMP_IMM(BPF_JA, 0, 0, 0);
> +static const struct bpf_insn MAY_GOTO_0 = BPF_RAW_INSN(BPF_JMP |
> BPF_JCOND, 0, 0, 0, 0);
This actually is what I did initially. I changed to use the stack var because
NOP is used in other functions too while MAY_GOTO_0 is only used in
opt_remove_nops(). Certainly, using MAY_GOTO_0 as static variable works too.
>
> static int opt_remove_nops(struct bpf_verifier_env *env)
> {
> - const struct bpf_insn ja = NOP;
> struct bpf_insn *insn = env->prog->insnsi;
> int insn_cnt = env->prog->len;
> + bool is_ja, is_may_goto_0;
> int i, err;
>
> for (i = 0; i < insn_cnt; i++) {
> - if (memcmp(&insn[i], &ja, sizeof(ja)))
> + is_may_goto_0 = !memcmp(&insn[i], &MAY_GOTO_0,
> sizeof(MAY_GOTO_0));
> + is_ja = !memcmp(&insn[i], &NOP, sizeof(NOP));
> + if (!is_may_goto_0 && !is_ja)
> continue;
>
>> err = verifier_remove_insns(env, i, 1);
>> if (err)
>> return err;
>> insn_cnt--;
>> - i--;
>> + i -= (is_may_goto_0 && i > 0) ? 2 : 1;
>
> Maybe add a comment for this logic?
Thanks Alexei for adding comments before merging!
>
> Thanks,
> Daniel
next prev parent reply other threads:[~2025-01-21 3:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-18 19:20 [PATCH bpf-next v2 0/3] bpf: Allow 'may_goto 0' instruction Yonghong Song
2025-01-18 19:20 ` [PATCH bpf-next v2 1/3] bpf: Allow 'may_goto 0' instruction in verifier Yonghong Song
2025-01-20 15:20 ` Daniel Borkmann
2025-01-18 19:20 ` [PATCH bpf-next v2 2/3] bpf: Remove 'may_goto 0' instruction in opt_remove_nops() Yonghong Song
2025-01-20 15:29 ` Daniel Borkmann
2025-01-20 17:49 ` Alexei Starovoitov
2025-01-21 3:20 ` Yonghong Song [this message]
2025-01-18 19:20 ` [PATCH bpf-next v2 3/3] selftests/bpf: Add some tests related to 'may_goto 0' insns Yonghong Song
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=4e621ff0-c40f-44ed-9610-8eadfd9f3cf1@linux.dev \
--to=yonghong.song@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=martin.lau@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