From: Qiliang Yuan <realwujing@gmail.com>
To: menglong.dong@linux.dev
Cc: alexei.starovoitov@gmail.com, andrii@kernel.org, ast@kernel.org,
bpf@vger.kernel.org, daniel@iogearbox.net, eddyz87@gmail.com,
haoluo@google.com, john.fastabend@gmail.com, jolsa@kernel.org,
kpsingh@kernel.org, linux-kernel@vger.kernel.org,
martin.lau@linux.dev, memxor@gmail.com, realwujing@gmail.com,
realwujing@qq.com, sdf@fomichev.me, song@kernel.org,
yonghong.song@linux.dev, yuanql9@chinatelecom.cn
Subject: Re: [PATCH v2] bpf/verifier: implement slab cache for verifier state list
Date: Sun, 18 Jan 2026 17:46:36 +0800 [thread overview]
Message-ID: <20260118094636.105625-1-realwujing@gmail.com> (raw)
In-Reply-To: <6205668.MhkbZ0Pkbq@7950hx>
On Sat, Jan 17, 2026 at 7:27 PM, Menglong Dong <menglong.dong@linux.dev> wrote:
>You can put the link of your previous version to the change log. I
>suspect the patchwork can't even detect this new version if you send
>it as a reply.
That's because I used another username and email address before.
>You introduce the slab cache to speed up the verifier, so I think we need
>a comparison, such as how long a complex BPF program can take in
>the verifier. If it is no more than 1ms, then I think it doesn't make much
>sense to obtain the 5% speeding up. After all, it's not a BPF runtime
>overhead.
However, this patch can accelerate the bpf verifier, and the same idea we can use to
accelerate the bpf runtime.
>I think we don't do it this way, and it makes the patch look a mess. You can
>reply directly in the mail.
You can see the guide of --- from this url:
https://www.kernel.org/doc/html/latest/process/submitting-patches.html#commentary
Best regards,
Qiliang
prev parent reply other threads:[~2026-01-18 9:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 12:24 [PATCH] " wujing
2026-01-12 18:15 ` Kumar Kartikeya Dwivedi
2026-01-14 8:28 ` [PATCH bpf-next] " wujing
2026-01-14 15:59 ` Alexei Starovoitov
2026-01-15 3:19 ` wujing
2026-01-16 13:29 ` [PATCH v2] " Qiliang Yuan
2026-01-16 14:50 ` Menglong Dong
2026-01-17 3:26 ` Qiliang Yuan
2026-01-17 6:24 ` Alexei Starovoitov
2026-01-17 11:08 ` Menglong Dong
2026-01-17 11:27 ` Menglong Dong
2026-01-18 9:46 ` Qiliang Yuan [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=20260118094636.105625-1-realwujing@gmail.com \
--to=realwujing@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=menglong.dong@linux.dev \
--cc=realwujing@qq.com \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
--cc=yuanql9@chinatelecom.cn \
/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
all inboxes | Powered by JetHome®