[dpdk-ci] Community CI Meeting Minutes - August 27, 2020
Ali Alnubani
alialnu at nvidia.com
Tue Sep 1 15:16:39 CEST 2020
Hi,
> -----Original Message-----
> From: ci <ci-bounces at dpdk.org> On Behalf Of Lincoln Lavoie
> Sent: Thursday, August 27, 2020 9:50 PM
> To: ci at dpdk.org
> Subject: [dpdk-ci] Community CI Meeting Minutes - August 27, 2020
>
> August 27, 2020
>
<snip>
>
> Features in Progress
<snip>
> 4. Module EEPROM Dump
> * Patch submitted to dpdk to add functionality in the testpmd to allow
> output of EEPROM, we will implement feedback received on the patch.
> * There is a limited way to test this feature, because the
> returned PROM data is opaque. One option could use tools external to
> DPDK to also download PROM, then compare the images. But that would
> add additional dependencies to DTS for what tools need to be available on
> the DUT.
I agree with just comparing to the output of other programs. We can use 'ethtool' for that, which I believe already comes pre-installed in most distributions, and is already a dependency for DTS.
> 5. Rte_flow
> * We are currently looking into the scope of the API and the few test
> cases that already touch the API to develop the list of test cases.
> * Tests will need to allow for different supported actions on each NIC /
> driver. Release notes for each PMD should list the support actions.
>
I think I confused the release notes with PMD documentation when I suggested this (sorry about that), and I think it's going to be less obvious to figure out which actions/items are supported per PMD/NIC.
For MLX5, the supported actions are in the table in this section https://doc.dpdk.org/guides/nics/mlx5.html#supported-hardware-offloads, but other PMDs might not use the same documentation format.
I will try to collect and provide more information to help with what's supported (or not) on the Mellanox NICs.
Regards,
Ali
More information about the ci
mailing list