From: Thomas Monjalon <thomas@monjalon.net>
To: Andrew Bailey <abailey@iol.unh.edu>
Cc: probb@iol.unh.edu, 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:55:40 +0100 [thread overview]
Message-ID: <2341241.iZASKD2KPV@thomas> (raw)
In-Reply-To: <CABJ3N2XxFso=mKLObZzy5bPiLDRewNmNU=15WCh2koz=4EdnqA@mail.gmail.com>
12/03/2026 19:48, Andrew Bailey:
> On Thu, Mar 12, 2026 at 2:08 PM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> > 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?
> >
>
> I agree that "crypto" is not exactly a true description of the
> purpose for this test type. It is probably better for the test type
> to explicitly describe it's purpose. maybe NO_GEN/NO_GENERATOR
> or NO_TG. It just so happens with this series that crypto tests are the
> only cases with this type, which was the cause for the initial name
> but should change in the future. Furthermore, we could divide this
> into performance and functional versions of this flag.
Yes I think we need to consider the level of abstraction required here,
and the cases we want to cover.
next prev parent reply other threads:[~2026-03-12 18:55 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
2026-03-12 18:48 ` Andrew Bailey
2026-03-12 18:55 ` Thomas Monjalon [this message]
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=2341241.iZASKD2KPV@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