[dpdk-dev] [PATCH v1 8/8] crypto/bcmfs: add crypto pmd into cryptodev test

Dybkowski, AdamX adamx.dybkowski at intel.com
Wed Aug 12 15:44:38 CEST 2020


> -----Original Message-----
> From: dev <dev-bounces at dpdk.org> On Behalf Of Vikas Gupta
> Sent: Wednesday, 12 August, 2020 08:31
> To: dev at dpdk.org; akhil.goyal at nxp.com
> Cc: ajit.khaparde at broadcom.com; vikram.prakash at broadcom.com; Vikas
> Gupta <vikas.gupta at broadcom.com>; Raveendra Padasalagi
> <raveendra.padasalagi at broadcom.com>
> Subject: [dpdk-dev] [PATCH v1 8/8] crypto/bcmfs: add crypto pmd into
> cryptodev test
> 
> Add test suites for supported algorithms by bcmfs crypto pmd
> 
> Signed-off-by: Vikas Gupta <vikas.gupta at broadcom.com>
> Signed-off-by: Raveendra Padasalagi
> <raveendra.padasalagi at broadcom.com>
> Reviewed-by: Ajit Khaparde <ajit.khaparde at broadcom.com>
> ---
>  app/test/test_cryptodev.c | 261

[Adam] The test suites set was refactored in recent months to use one big list of tests and run/skip them depending on the capability checks. I strongly propose to do this also for your new BCMFS PMD. Have a look at e.g. QAT PMD test suite in the same file. It has one function to properly initialize the run (check the device id) and then it uses big common area of individual tests (some of them are skipped because of requiring specific capabilities).

Adam Dybkowski



More information about the dev mailing list