From: Ali Alnubani <alialnu@nvidia.com>
To: Lincoln Lavoie <lylavoie@iol.unh.edu>,
Brandon Lo <blo@iol.unh.edu>, "David Liu" <dliu@iol.unh.edu>
Cc: "ci@dpdk.org" <ci@dpdk.org>
Subject: Re: [dpdk-ci] Community CI Meeting Minutes - August 27, 2020
Date: Tue, 1 Sep 2020 13:16:39 +0000 [thread overview]
Message-ID: <BN6PR12MB12835FED75394C632F781236DA2E0@BN6PR12MB1283.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAOE1vsPud-6CZ+u_s6XxduwUoQsvJqKYJ-0KnFr=aP1yY+5-gA@mail.gmail.com>
Hi,
> -----Original Message-----
> From: ci <ci-bounces@dpdk.org> On Behalf Of Lincoln Lavoie
> Sent: Thursday, August 27, 2020 9:50 PM
> To: ci@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
next prev parent reply other threads:[~2020-09-01 13:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 18:49 Lincoln Lavoie
2020-09-01 13:16 ` Ali Alnubani [this message]
2020-09-02 20:43 ` Thomas Monjalon
2020-09-02 21:22 ` Lincoln Lavoie
2020-09-02 21:25 ` Thomas Monjalon
2020-09-02 21:28 ` Lincoln Lavoie
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=BN6PR12MB12835FED75394C632F781236DA2E0@BN6PR12MB1283.namprd12.prod.outlook.com \
--to=alialnu@nvidia.com \
--cc=blo@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=dliu@iol.unh.edu \
--cc=lylavoie@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;
as well as URLs for NNTP newsgroup(s).