From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1352] Port driver rebinding
Date: Wed, 10 Jan 2024 09:51:27 +0000 [thread overview]
Message-ID: <bug-1352-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1882 bytes --]
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: dev@dpdk.org
Reporter: juraj.linkes@pantheon.tech
CC: juraj.linkes@pantheon.tech, probb@iol.unh.edu
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.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3804 bytes --]
reply other threads:[~2024-01-10 9:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-1352-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/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).