From: Thomas Monjalon <thomas@monjalon.net>
To: probb@iol.unh.edu, Andrew Bailey <abailey@iol.unh.edu>
Cc: dev@dpdk.org, luca.vizzarro@arm.com, dmarx@iol.unh.edu,
kai.ji@intel.com, dharmikjayesh.thakkar@arm.com,
david.marchand@redhat.com, gakhil@marvell.com
Subject: Re: [PATCH v5 5/5] dts: add crypto test decorator
Date: Thu, 12 Mar 2026 19:08:17 +0100 [thread overview]
Message-ID: <8652174.T7Z3S40VBb@thomas> (raw)
In-Reply-To: <20260306164027.171723-6-abailey@iol.unh.edu>
06/03/2026 17:40, Andrew Bailey:
> Currently, a test case is decorated to signify whether to use Scapy or
> TREX. This change allows test suites that do not use a traffic generator
> to avoid the overhead of initializing either one.
[...]
> if (tt.test_type is TestCaseType.FUNCTIONAL and self.func)
> or (tt.test_type is TestCaseType.PERFORMANCE and self.perf)
> + or (tt.test_type is TestCaseType.CRYPTO and self.crypto)
That's a bit strange to read,
because a crypto test can be functional or performance.
I suppose we can re-discuss the classification of the tests.
If the only need here is about the traffic generator,
we could make it "raw input" or something like that?
next prev parent reply other threads:[~2026-03-12 18:08 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 19:34 [PATCH v2 0/5] dts: add cryptodev testing support Andrew Bailey
2026-02-10 19:34 ` [PATCH v2 1/5] dts: add find float method to text parser Andrew Bailey
2026-02-10 19:34 ` [PATCH v2 2/5] dts: add cryptodev package to DTS Andrew Bailey
2026-02-10 19:34 ` [PATCH v2 3/5] dts: add cryptodev throughput test suite Andrew Bailey
2026-02-10 19:34 ` [PATCH v2 4/5] dts: add crypto test decorator Andrew Bailey
2026-02-10 19:34 ` [PATCH v2 5/5] dts: automate VFIO-PCI modprobe in node setup Andrew Bailey
2026-02-13 19:35 ` [PATCH v3 0/5] dts: add cryptodev testing support Andrew Bailey
2026-02-13 19:35 ` [PATCH v3 1/5] dts: add find float method to text parser Andrew Bailey
2026-02-25 21:05 ` Patrick Robb
2026-02-13 19:35 ` [PATCH v3 2/5] dts: add cryptodev package to DTS Andrew Bailey
2026-02-25 21:06 ` Patrick Robb
2026-02-26 19:13 ` Andrew Bailey
2026-02-27 16:15 ` Patrick Robb
2026-02-13 19:35 ` [PATCH v3 3/5] dts: add cryptodev throughput test suite Andrew Bailey
2026-02-27 18:24 ` Patrick Robb
2026-02-27 19:43 ` Andrew Bailey
2026-02-13 19:35 ` [PATCH v3 4/5] dts: add crypto test decorator Andrew Bailey
2026-02-27 18:28 ` Patrick Robb
2026-02-27 19:18 ` Andrew Bailey
2026-02-13 19:35 ` [PATCH v3 5/5] dts: automate VFIO-PCI modprobe in node setup Andrew Bailey
2026-02-27 18:33 ` Patrick Robb
2026-03-02 18:54 ` [PATCH v4 0/5] dts: add cryptodev testing support Andrew Bailey
2026-03-02 18:54 ` [PATCH v4 1/5] dts: add find float method to text parser Andrew Bailey
2026-03-02 18:54 ` [PATCH v4 2/5] dts: automate VFIO-PCI modprobe in node setup Andrew Bailey
2026-03-02 18:54 ` [PATCH v4 3/5] dts: add cryptodev package to DTS Andrew Bailey
2026-03-02 18:54 ` [PATCH v4 4/5] dts: add cryptodev throughput test suite Andrew Bailey
2026-03-05 19:26 ` Patrick Robb
2026-03-05 20:20 ` Patrick Robb
2026-03-02 18:54 ` [PATCH v4 5/5] dts: add crypto test decorator Andrew Bailey
2026-03-06 16:40 ` [PATCH v5 0/5] dts: add cryptodev testing support Andrew Bailey
2026-03-06 16:40 ` [PATCH v5 1/5] dts: add find float method to text parser Andrew Bailey
2026-03-06 16:40 ` [PATCH v5 2/5] dts: automate VFIO-PCI modprobe in node setup Andrew Bailey
2026-03-06 16:40 ` [PATCH v5 3/5] dts: add cryptodev package to DTS Andrew Bailey
2026-03-09 1:26 ` Patrick Robb
2026-03-06 16:40 ` [PATCH v5 4/5] dts: add cryptodev throughput test suite Andrew Bailey
2026-03-06 16:40 ` [PATCH v5 5/5] dts: add crypto test decorator Andrew Bailey
2026-03-12 18:08 ` Thomas Monjalon [this message]
2026-03-12 18:48 ` Andrew Bailey
2026-03-12 18:55 ` Thomas Monjalon
2026-03-12 19:54 ` Patrick Robb
2026-03-12 20:29 ` Thomas Monjalon
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=8652174.T7Z3S40VBb@thomas \
--to=thomas@monjalon.net \
--cc=abailey@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dharmikjayesh.thakkar@arm.com \
--cc=dmarx@iol.unh.edu \
--cc=gakhil@marvell.com \
--cc=kai.ji@intel.com \
--cc=luca.vizzarro@arm.com \
--cc=probb@iol.unh.edu \
/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