From: Marat Khalili <marat.khalili@huawei.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [RFC] test: split up BPF tests
Date: Fri, 23 Jan 2026 10:44:19 +0000 [thread overview]
Message-ID: <7207dfbe4aa74311aee79389af885703@huawei.com> (raw)
In-Reply-To: <20260122193923.49253-1-stephen@networkplumber.org>
> The BPF tests have two sections. One is doing tests of the
> BPF interpreter and the other is for testing the ELF load part.
> The latter requires the null PMD to work, so only build it
> present.
Splitting BPF tests into multiple files makes sense, and not just because of
dependencies.
Coupling ELF tests with the presence of null PMD is strange, there might be a
lot of BPF ELF tests that do not depend on null or any PMD, and there might be
other BPF tests depending on PMD. Maybe we should call the new file
test_bpf_ethdev.c instead (following the header name rte_bpf_ethdev.h ,
regardless of what one thinks of the name), or something like this.
next prev parent reply other threads:[~2026-01-23 10:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 19:39 [RFC] test: split up BPF tests Stephen Hemminger
2026-01-23 10:44 ` Marat Khalili [this message]
2026-01-24 17:12 ` Stephen Hemminger
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=7207dfbe4aa74311aee79389af885703@huawei.com \
--to=marat.khalili@huawei.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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