DPDK patches and discussions
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-1200-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 1319 bytes --]

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

            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 = &txq->cqes[txq->cq_ci & txq->cqe_m];
                ret = check_cqe(cqe, txq->cqe_s, txq->cq_ci);
+    if (ret==MLX5_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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 3239 bytes --]

             reply	other threads:[~2023-03-24 23:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24 23:03 bugzilla [this message]
2023-03-27 22:39 ` bugzilla

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-1200-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).