From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id A783943881; Wed, 10 Jan 2024 10:51:28 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 4004640298; Wed, 10 Jan 2024 10:51:28 +0100 (CET) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id 7889040269 for ; Wed, 10 Jan 2024 10:51:27 +0100 (CET) Received: by inbox.dpdk.org (Postfix, from userid 33) id 46A8643882; Wed, 10 Jan 2024 10:51:27 +0100 (CET) From: bugzilla@dpdk.org To: dev@dpdk.org Subject: [Bug 1352] Port driver rebinding Date: Wed, 10 Jan 2024 09:51:27 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: dts X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: juraj.linkes@pantheon.tech X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc target_milestone Message-ID: Content-Type: multipart/alternative; boundary=17048802870.CCC77Cf.2462919 Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --17048802870.CCC77Cf.2462919 Date: Wed, 10 Jan 2024 10:51:27 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All https://bugs.dpdk.org/show_bug.cgi?id=3D1352 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, wh= ich will be removed. The rebinding is basically a workaround so that the test s= uite is functional until removed. We need to solidify our DTS port rebinding policy - do we want to rebind an= d if so, under what circumstances. The current considerations are: 1. Don't modify the DUT/server configuration if not explicitly asked. The p= ort binding could be configurable in which case we could do the rebinding inste= ad of just checking the right port in the smoke tests (maybe in the smoke test= s, maybe separately beforehand). 2. We want to be able to run both functional and performance tests in one D= TS 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 testi= ng). This clashes with the requirement for explicit consent for rebinding, but i= f 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. --=20 You are receiving this mail because: You are the assignee for the bug.= --17048802870.CCC77Cf.2462919 Date: Wed, 10 Jan 2024 10:51:27 +0100 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All
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 rebindi=
ng in the temporary os_udp test suite, which
will be removed. The rebinding is basically a workaround so that the test s=
uite
is functional until removed.

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

The current considerations are:
1. Don't modify the DUT/server configuration if not explicitly asked. The p=
ort
binding could be configurable in which case we could do the rebinding inste=
ad
of just checking the right port in the smoke tests (maybe in the smoke test=
s,
maybe separately beforehand).
2. We want to be able to run both functional and performance tests in one D=
TS
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 testi=
ng).
This clashes with the requirement for explicit consent for rebinding, but i=
f 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.
=20=20=20=20=20=20=20=20=20=20
= --17048802870.CCC77Cf.2462919--