Skip to contentSkip to conversation

Port driver rebinding

Bug 1352 [email protected] 1 participant 2 messages Jan 10, 2024 – Dec 18, 2025

lore
Share & tools
lore

[email protected]

author
#0 lore raw

https://bugs.dpdk.org/show_bug.cgi?id=1352

Bug ID: 1352
Summary: Port driver rebinding
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: dts
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected]
Target Milestone: ---

We're currently using port rebinding in the temporary os_udp test suite, which will be removed. The rebinding is basically a workaround so that the test suite is functional until removed.

We need to solidify our DTS port rebinding policy - do we want to rebind and if so, under what circumstances.

The current considerations are:
1. Don't modify the DUT/server configuration if not explicitly asked. The port binding could be configurable in which case we could do the rebinding instead of just checking the right port in the smoke tests (maybe in the smoke tests, maybe separately beforehand).
2. We want to be able to run both functional and performance tests in one DTS run. In this case, we must be able to rebind in case we need to use two different traffic generators which require different drivers (as is the case with Scapy for functional testing and T-rex/DPDK tgen for performance testing). This clashes with the requirement for explicit consent for rebinding, but if we properly document (in all places - the docs, config, code) that func+perf testing implies DTS can rebind for this purpose, it could be a sensible exception. The rebinding would be done only twice, once between functional and performance test cases and once to revert back to original.

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.
author
#1 lore raw

http://bugs.dpdk.org/show_bug.cgi?id=1352

Andrew ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

                 CC|                            |[email protected]
         Resolution|---                         |FIXED
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #8 from Andrew ([email protected]) ---
There has been a patch resolving this issue that is merged into main.

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.