[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20260118094636.105625-1-realwujing@gmail.com>
Date: Sun, 18 Jan 2026 17:46:36 +0800
From: Qiliang Yuan <realwujing@...il.com>
To: menglong.dong@...ux.dev
Cc: alexei.starovoitov@...il.com,
andrii@...nel.org,
ast@...nel.org,
bpf@...r.kernel.org,
daniel@...earbox.net,
eddyz87@...il.com,
haoluo@...gle.com,
john.fastabend@...il.com,
jolsa@...nel.org,
kpsingh@...nel.org,
linux-kernel@...r.kernel.org,
martin.lau@...ux.dev,
memxor@...il.com,
realwujing@...il.com,
realwujing@...com,
sdf@...ichev.me,
song@...nel.org,
yonghong.song@...ux.dev,
yuanql9@...natelecom.cn
Subject: Re: [PATCH v2] bpf/verifier: implement slab cache for verifier state list
On Sat, Jan 17, 2026 at 7:27 PM, Menglong Dong <menglong.dong@...ux.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
Powered by blists - more mailing lists