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 B2BC545A11; Mon, 23 Sep 2024 17:27:21 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 4CD044027C; Mon, 23 Sep 2024 17:27:21 +0200 (CEST) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id 96AEC40274 for ; Mon, 23 Sep 2024 17:27:19 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id 86C3045A13; Mon, 23 Sep 2024 17:27:19 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Subject: [DPDK/DTS Bug 1548] Add asynchronous output collector for testpmd verbose information Date: Mon, 23 Sep 2024 15:27:18 +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: jspewock@iol.unh.edu 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=17271052391.41Bdf3418.3058291 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 --17271052391.41Bdf3418.3058291 Date: Mon, 23 Sep 2024 17:27:19 +0200 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=3D1548 Bug ID: 1548 Summary: Add asynchronous output collector for testpmd verbose information Product: DPDK Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: Normal Component: DTS Assignee: dev@dpdk.org Reporter: jspewock@iol.unh.edu CC: juraj.linkes@pantheon.tech, probb@iol.unh.edu Target Milestone: --- Verbose packets can be received at any point in time while packets are being forwarded in testpmd, but output collection in interactive shells doesn't support this behavior (or any asynchronous behavior for that matter). Curre= ntly the way that output collection works with interactive shells is after sendi= ng a command the framework will consume all output since the previous command th= at is in the buffer. In the case of verbose output in testpmd, this means that= if you send any command while verbose packet forwarding is turned on, you will consume and discard all of the verbose information that was sent to stdout prior to that command being sent. There are a few ways to handle this, one way that was proposed was just to ensure that testpmd methods always return their raw output so that it can be parsed, another was to track if verbose output is being sent and, if it is, collecting it from every command that is sent so that it can be read later = [1]. The second method seems preferred, but if it is done that way there should = be some method of time-stamping when each blob of verbose output was collected= so that developers have the ability to examine verbose output specifically bet= ween two command, rather than all of the output gathered thus far. [1] https://inbox.dpdk.org/dev/CAKXZ7egonYtTivf-SZB=3Dixv+Utgpww8Sku9Jy8xj58mgV= 4KNwQ@mail.gmail.com/ --=20 You are receiving this mail because: You are the assignee for the bug.= --17271052391.41Bdf3418.3058291 Date: Mon, 23 Sep 2024 17:27:19 +0200 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 1548
Summary Add asynchronous output collector for testpmd verbose informa= tion
Product DPDK
Version unspecified
Hardware All
OS All
Status UNCONFIRMED
Severity normal
Priority Normal
Component DTS
Assignee dev@dpdk.org
Reporter jspewock@iol.unh.edu
CC juraj.linkes@pantheon.tech, probb@iol.unh.edu
Target Milestone --- 

Verbose packets can be received at=
 any point in time while packets are being
forwarded in testpmd, but output collection in interactive shells doesn't
support this behavior (or any asynchronous behavior for that matter). Curre=
ntly
the way that output collection works with interactive shells is after sendi=
ng a
command the framework will consume all output since the previous command th=
at
is in the buffer. In the case of verbose output in testpmd, this means that=
 if
you send any command while verbose packet forwarding is turned on, you will
consume and discard all of the verbose information that was sent to stdout
prior to that command being sent.

There are a few ways to handle this, one way that was proposed was just to
ensure that testpmd methods always return their raw output so that it can be
parsed, another was to track if verbose output is being sent and, if it is,
collecting it from every command that is sent so that it can be read later =
[1].
The second method seems preferred, but if it is done that way there should =
be
some method of time-stamping when each blob of verbose output was collected=
 so
that developers have the ability to examine verbose output specifically bet=
ween
two command, rather than all of the output gathered thus far.

[1]
https://inbox.dpdk.org/dev/CAKXZ7egon=
YtTivf-SZB=3Dixv+Utgpww8Sku9Jy8xj58mgV4KNwQ@mail.gmail.com/

You are receiving this mail because:
  • You are the assignee for the bug.
=20=20=20=20=20=20=20=20=20=20
= --17271052391.41Bdf3418.3058291--