[PATCH 1/1] Cn10K crypto Tests: Added Marvell Cn10K specific crypto Tests to TestCryptoPerfCryptodevPerf

David Marchand david.marchand at redhat.com
Thu Oct 31 11:09:39 CET 2024


Hello Gnanesh,

On Wed, Oct 30, 2024 at 5:44 PM Gnanesh <gpalanethra at marvell.com> wrote:
>
>     Changes included in this patch:
>     -- New TestCases are added for Cn10K CPT Hardware crypto accelerator.
>     -- when Testing newly added Testcases it is found Necessary to make Below Changes
>           1> tests/cryptodev_common.py
>                --> bind_qat_device function is updated to generate VFs for the given crypto_dev_id
>                --> added New function bind_mrvl_devices to accept list of PCI Ids and bind it to vfio_pci driver.
>           2> framework/crb.py
>                --> updated pci_devices_information_uncached_linux Method to handle additional Nic Speeds for Cavium,
>                    as it was restricting only to 1 GIG NIC speed
>           3> framework/settings.py
>                --> Changed the default Cavium NIC driver to rvu_nicpf.
>           4> nics/net_device.py
>                --> added Missing expect object
>           5> conf/crypto_perf_cryptodev_perf.cfg
>                --> added Marvell Cn10K configs for crypto_perf_cryptodev_perf
>           6> framework/ssh_pexpect.py
>                --> output.replace command's output is not set before returning from get_output_all method
>                    hence Unnecessarily returning Prompt along with the output
>           7> tests/TestSuite_crypto_perf_cryptodev_perf.py
>                -->  added Marvell CN10K Testcases
>              Updated Below Private functions
>                 6.1> _run_crypto_perf() --> receives additional KW arguments
>                 6.2> _parse_output()  ---> Updated to handle Marvell Cn10K app command output
>                 6.3> _run_crypto_perf_throughput() --> receives additional KW arguments
>
>
> Signed-off-by: Gnanesh <gpalanethra at marvell.com>

This mailing list is not used anymore.
If you want to reach out to current DTS maintainers, you should send
mail to dev at dpdk.org (I Cc'd Paul and Patrick).


-- 
David Marchand



More information about the dts mailing list