DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Vizzarro <Luca.Vizzarro@arm.com>
To: Andrew Bailey <abailey@iol.unh.edu>,
	dev@dpdk.org, patrickrobb1997@gmail.com, dladd@iol.unh.edu
Cc: knimoji@iol.unh.edu, lylavoie@iol.unh.edu
Subject: Re: [PATCH v3 1/2] dts: refactor cryptodev throughput test suite
Date: Fri, 30 Oct 2026 11:52:53 +0000	[thread overview]
Message-ID: <63b5c4bc-e6ad-4a53-8045-afc48cfbe6fa@arm.com> (raw)
In-Reply-To: <20261019200424.898640-1-abailey@iol.unh.edu>

On 19/10/2026 21:04, Andrew Bailey wrote:
>   class Config(BaseConfig):
>       """Performance test metrics.
>   
>       Attributes:
>           delta_tolerance: The allowed tolerance below a given baseline.
> -        throughput_test_parameters: The test parameters to use in the test suite.
> +        test_combinations: List of test combinations with cipher/auth algorithms and parameters.
>       """
Hey Andrew,

The refactor looks mostly fine. Even though it was previously merged 
like that, can we use this refactor to appropriately define the 
configuration of the test suite. Given this is not a simple TypedDict, 
you could perhaps use a Pydantic model to define the fields. just a 
dict[str, ...] is too vague and compromises configuration validation 
upon startup. Moreover the Pydantic-based configurations will render 
appropriately in the docs, so the user will know better how to configure 
that way. You can have a look at the config module to see how it was done.

Luca

      parent reply	other threads:[~2026-10-30 11:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27 17:22 [PATCH v1] dts: refactor cryptodev throughput test suite Andrew Bailey
2026-09-28 18:06 ` [PATCH v2 1/2] " Andrew Bailey
2026-09-28 18:06   ` [PATCH v2 2/2] dts: refactor cryptodev latency " Andrew Bailey
2026-10-19 20:04 ` [PATCH v3 1/2] dts: refactor cryptodev throughput " Andrew Bailey
2026-10-19 20:04   ` [PATCH v3 2/2] dts: refactor cryptodev latency " Andrew Bailey
2026-10-27 16:21     ` Koushik Bhargav Nimoji
2026-10-30 11:53     ` Luca Vizzarro
2026-10-27 13:40   ` [PATCH v3 1/2] dts: refactor cryptodev throughput " Koushik Bhargav Nimoji
2026-10-30 11:59     ` Luca Vizzarro
2026-10-30 11:52   ` Luca Vizzarro [this message]

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=63b5c4bc-e6ad-4a53-8045-afc48cfbe6fa@arm.com \
    --to=luca.vizzarro@arm.com \
    --cc=abailey@iol.unh.edu \
    --cc=dev@dpdk.org \
    --cc=dladd@iol.unh.edu \
    --cc=knimoji@iol.unh.edu \
    --cc=lylavoie@iol.unh.edu \
    --cc=patrickrobb1997@gmail.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