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 9134E42818; Sat, 25 Mar 2023 00:03:16 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6D17B40EE5; Sat, 25 Mar 2023 00:03:16 +0100 (CET) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id C192940E0F for ; Sat, 25 Mar 2023 00:03:15 +0100 (CET) Received: by inbox.dpdk.org (Postfix, from userid 33) id B146142819; Sat, 25 Mar 2023 00:03:15 +0100 (CET) From: bugzilla@dpdk.org To: dev@dpdk.org Subject: [Bug 1200] mlx5_tx_handle_completion: bad timestamp Date: Fri, 24 Mar 2023 23:03:15 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: core X-Bugzilla-Version: 22.03 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: 7532yahoo@gmail.com 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 target_milestone Message-ID: Content-Type: multipart/alternative; boundary=16796989950.5a6C35BE6.2185626 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 --16796989950.5a6C35BE6.2185626 Date: Sat, 25 Mar 2023 00:03:15 +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=3D1200 Bug ID: 1200 Summary: mlx5_tx_handle_completion: bad timestamp Product: DPDK Version: 22.03 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: Normal Component: core Assignee: dev@dpdk.org Reporter: 7532yahoo@gmail.com Target Milestone: --- In the file `dpdk/drivers/net/mlx5/mlx5_tx.c` method `mlx5_tx_handle_completion` I inspect the timestamp field of a cqe: @@ -192,6 +196,9 @@ mlx5_tx_handle_completion(struct mlx5_txq_data *__rte_restrict txq, cqe =3D &txq->cqes[txq->cq_ci & txq->cqe_m]; ret =3D check_cqe(cqe, txq->cqe_s, txq->cq_ci); + if (ret=3D=3DMLX5_CQE_STATUS_HW_OWN) { + printf("line:%d cqe timestamp: %lu\n", __LINE__, cqe->timestamp); + } Consider transmitting several thousand packets. This print to stdout with regard to the timestamp, * prints 0 for timestamp for the first ~2000 packet completions * prints non-zero numbers thereafter, however, not monotonically increasing e.g. completion event timestamp for occurrence N is 10x smaller than N-1 --=20 You are receiving this mail because: You are the assignee for the bug.= --16796989950.5a6C35BE6.2185626 Date: Sat, 25 Mar 2023 00:03:15 +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	1200
Summary	mlx5_tx_handle_completion: bad timestamp
Product	DPDK
Version	22.03
Hardware	x86
OS	Linux
Status	UNCONFIRMED
Severity	normal
Priority	Normal
Component	core
Assignee	dev@dpdk.org
Reporter	7532yahoo@gmail.com
Target Milestone	---

In the file `dpdk/drivers/net/mlx5=
/mlx5_tx.c` method
`mlx5_tx_handle_completion` I inspect the timestamp field of a cqe:

@@ -192,6 +196,9 @@ mlx5_tx_handle_completion(struct mlx5_t=
xq_data
*__rte_restrict txq,

                cqe =3D &txq->cqes[txq->cq_ci & txq->cqe_m=
];
                ret =3D check_cqe(cqe, txq->cqe_s, txq->cq_ci);
+    if (ret=3D=3DMLX5_CQE_STATUS_HW_OWN) {
+      printf("line:%d cqe timestamp: %lu\n", __LINE__, cqe->t=
imestamp);
+    }

Consider transmitting several thousand packets. This print to stdout with
regard to the timestamp,

* prints 0 for timestamp for the first ~2000 packet completions
* prints non-zero numbers thereafter, however, not monotonically increasing
e.g. completion event timestamp for occurrence  N is 10x smaller than N-1

You are receiving this mail because:

You are the assignee for the bug.

=20=20=20=20=20=20=20=20=20=20

= --16796989950.5a6C35BE6.2185626--