From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Yoav Winstein <yoav.w@claroty.com>
Subject: |WARNING| pw140025 [PATCH] bpf: don't verify classic bpfs
Date: Sun, 12 May 2024 07:53:02 +0200 (CEST) [thread overview]
Message-ID: <20240512055303.04EB2121E57@dpdk.org> (raw)
In-Reply-To: <20240512055109.96609-1-yoav.w@claroty.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/140025
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#98:
I noticed that when classic BPFs with lots of branching instructions are compiled, __rte_bpf_bpf_validate runs way too slow. A simple bpf such as: 'ether host a0:38:6d:af:17:eb or b3:a3:ff:b6:c1:ef or ...' 12 times results in ~1 minute of bpf validation. This patch makes __rte_bpf_bpf_validate be aware of bpf_prm originating from classic BPF, allowing to safely skip over the validation.
ERROR:TRAILING_WHITESPACE: trailing whitespace
#151: FILE: lib/bpf/bpf_load.c:119:
+^I$
total: 1 errors, 1 warnings, 39 lines checked
next prev parent reply other threads:[~2024-05-12 5:53 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240512055109.96609-1-yoav.w@claroty.com>
2024-05-12 5:25 ` |SUCCESS| " qemudev
2024-05-12 5:29 ` qemudev
2024-05-12 5:53 ` checkpatch [this message]
2024-05-12 6:43 ` |FAILURE| " 0-day Robot
2024-05-13 12:11 ` |SUCCESS| " dpdklab
2024-05-13 12:24 ` dpdklab
2024-05-13 12:25 ` dpdklab
2024-05-13 12:25 ` dpdklab
2024-05-13 12:29 ` dpdklab
2024-05-13 12:32 ` dpdklab
2024-05-13 12:33 ` |WARNING| " dpdklab
2024-05-13 12:38 ` |SUCCESS| " dpdklab
2024-05-13 12:47 ` |WARNING| " dpdklab
2024-05-13 12:48 ` dpdklab
2024-05-13 12:48 ` |SUCCESS| " dpdklab
2024-05-13 12:49 ` |WARNING| " dpdklab
2024-05-13 12:49 ` dpdklab
2024-05-13 12:57 ` dpdklab
2024-05-13 12:59 ` dpdklab
2024-05-13 13:00 ` |SUCCESS| " dpdklab
2024-05-13 13:01 ` dpdklab
2024-05-13 13:02 ` |WARNING| " dpdklab
2024-05-13 13:02 ` |SUCCESS| " dpdklab
2024-05-13 13:03 ` dpdklab
2024-05-13 13:03 ` dpdklab
2024-05-13 13:03 ` dpdklab
2024-05-13 13:04 ` dpdklab
2024-05-13 13:04 ` dpdklab
2024-05-13 13:05 ` |WARNING| " dpdklab
2024-05-13 13:09 ` |SUCCESS| " dpdklab
2024-05-13 13:10 ` dpdklab
2024-05-13 13:10 ` dpdklab
2024-05-13 13:10 ` |WARNING| " dpdklab
2024-05-13 13:11 ` |SUCCESS| " dpdklab
2024-05-13 13:14 ` |WARNING| " dpdklab
2024-05-13 13:15 ` |SUCCESS| " dpdklab
2024-05-13 13:15 ` dpdklab
2024-05-13 13:15 ` dpdklab
2024-05-13 13:16 ` dpdklab
2024-05-13 13:16 ` dpdklab
2024-05-13 13:17 ` dpdklab
2024-05-13 13:17 ` dpdklab
2024-05-13 13:17 ` dpdklab
2024-05-13 13:18 ` dpdklab
2024-05-13 13:18 ` dpdklab
2024-05-13 13:19 ` dpdklab
2024-05-13 13:19 ` dpdklab
2024-05-13 13:20 ` dpdklab
2024-05-13 13:20 ` dpdklab
2024-05-13 13:20 ` dpdklab
2024-05-13 13:21 ` |WARNING| " dpdklab
2024-05-13 13:21 ` |SUCCESS| " dpdklab
2024-05-13 13:21 ` dpdklab
2024-05-13 13:21 ` dpdklab
2024-05-13 13:21 ` dpdklab
2024-05-13 13:22 ` dpdklab
2024-05-13 13:23 ` dpdklab
2024-05-13 13:23 ` dpdklab
2024-05-13 13:23 ` dpdklab
2024-05-13 13:23 ` dpdklab
2024-05-13 13:23 ` dpdklab
2024-05-13 13:23 ` dpdklab
2024-05-13 13:24 ` dpdklab
2024-05-13 13:24 ` dpdklab
2024-05-13 13:24 ` dpdklab
2024-05-13 13:24 ` dpdklab
2024-05-13 13:25 ` dpdklab
2024-05-13 13:25 ` dpdklab
2024-05-13 13:27 ` dpdklab
2024-05-13 13:28 ` dpdklab
2024-05-13 13:31 ` dpdklab
2024-05-13 13:32 ` dpdklab
2024-05-13 13:37 ` dpdklab
2024-05-13 13:37 ` dpdklab
2024-05-13 13:38 ` dpdklab
2024-05-13 13:38 ` dpdklab
2024-05-13 13:51 ` dpdklab
2024-05-13 13:55 ` dpdklab
2024-05-13 13:59 ` dpdklab
2024-05-13 14:01 ` dpdklab
2024-05-13 14:01 ` dpdklab
2024-05-13 14:04 ` dpdklab
2024-05-13 14:18 ` dpdklab
2024-05-13 14:21 ` dpdklab
2024-05-13 14:22 ` dpdklab
2024-05-13 14:26 ` dpdklab
2024-05-13 14:49 ` dpdklab
2024-05-13 15:25 ` dpdklab
2024-05-13 15:49 ` dpdklab
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=20240512055303.04EB2121E57@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=yoav.w@claroty.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;
as well as URLs for NNTP newsgroup(s).