FYI based on conversation with Dean I pushed a fixup adding
the use_virtual_functions: false field to the test_run.example.yaml, so
that users can more easily understand how to enable the VF testruns.
https://git.dpdk.org/next/dpdk-next-dts/commit/?id=934206f3bfc10fb8dcd852479f3683c01a18e352
Series applied to next-dts, thanks.
On Fri, Jul 4, 2025 at 12:25 AM Patrick Robb wrote:
> And FYI VF results for ConnectX-5 virtual functions for a testrun I just
> ran
>
> test_suites: ERROR
> vlan: PASS
> test_vlan_header_insertion: PASS
> test_vlan_no_receipt: PASS
> test_vlan_r
And FYI VF results for ConnectX-5 virtual functions for a testrun I just ran
test_suites: ERROR
vlan: PASS
test_vlan_header_insertion: PASS
test_vlan_no_receipt: PASS
test_vlan_receipt_no_stripping: PASS
test_vlan_receipt_stripping: PASS
rte_flow: FAIL
test_drop_action_ETH:
On Wed, Jul 2, 2025 at 12:23 PM Dean Marx wrote:
> Add virtual functions to DTS framework, along with
> a field for specifying VF test runs in the config file.
>
> Signed-off-by: Patrick Robb
> Signed-off-by: Dean Marx
> ---
> dts/framework/config/test_run.py | 2 +
> dts/framewor
During the process of writing these changes and testing virtual
functions on multiple environments, I came across some notable
behaviors. On Mellanox devices, the current test suites in DTS run
without issue, receiving and forwarding packets as expected. However,
this is not the case on Broadcom an
Add virtual functions to DTS framework, along with
a field for specifying VF test runs in the config file.
Signed-off-by: Patrick Robb
Signed-off-by: Dean Marx
---
dts/framework/config/test_run.py | 2 +
dts/framework/test_run.py| 7 +++
dts/framework/testbed_m
6 matches
Mail list logo
