From: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
To: <dev@dpdk.org>
Cc: <matan@nvidia.com>, <rasland@nvidia.com>, <orika@nvidia.com>,
<dsosnowski@nvidia.com>
Subject: [PATCH v2 0/4] net/mlx5: series to fix and improve tx trace capabilitie
Date: Mon, 14 Oct 2024 11:04:30 +0300 [thread overview]
Message-ID: <20241014080434.1211629-1-viacheslavo@nvidia.com> (raw)
In-Reply-To: <20241009114028.973284-1-viacheslavo@nvidia.com>
Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
---
v1: https://inbox.dpdk.org/dev/20241009114028.973284-1-viacheslavo@nvidia.com/
v2: move part of code between 2nd and 3rd patches to fix single patch compilation issue.
Tim Martin (2):
net/mlx5: fix real time counter reading from PCI BAR
net/mlx5: fix Tx tracing to use single clock source
Viacheslav Ovsiienko (2):
net/mlx5/tools: fix trace dump multiple burst completions
net/mlx5: update dump script to show incomplete records
.mailmap | 1 +
doc/guides/nics/mlx5.rst | 6 ++
drivers/net/mlx5/mlx5.c | 4 ++
drivers/net/mlx5/mlx5_trace.h | 9 ++-
drivers/net/mlx5/mlx5_tx.h | 53 ++++++++++++++--
drivers/net/mlx5/mlx5_txpp.c | 11 +---
drivers/net/mlx5/tools/mlx5_trace.py | 90 ++++++++++++++++++++--------
7 files changed, 133 insertions(+), 41 deletions(-)
--
2.34.1
next prev parent reply other threads:[~2024-10-14 8:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 11:40 [PATCH 0/4] net/mlx5: series to fix and improve tx trace capabilities Viacheslav Ovsiienko
2024-10-09 11:40 ` [PATCH 1/4] net/mlx5/tools: fix trace dump multiple burst completions Viacheslav Ovsiienko
2024-10-09 13:08 ` Dariusz Sosnowski
2024-10-09 11:40 ` [PATCH 2/4] net/mlx5: fix real time counter reading from PCI BAR Viacheslav Ovsiienko
2024-10-09 11:40 ` [PATCH 3/4] net/mlx5: fix Tx tracing to use single clock source Viacheslav Ovsiienko
2024-10-09 11:40 ` [PATCH 4/4] net/mlx5: update dump script to show incomplete records Viacheslav Ovsiienko
2024-10-09 13:08 ` Dariusz Sosnowski
2024-10-09 17:41 ` [PATCH 0/4] net/mlx5: series to fix and improve tx trace capabilities Stephen Hemminger
2024-10-14 8:04 ` Viacheslav Ovsiienko [this message]
2024-10-14 8:04 ` [PATCH v2 1/4] net/mlx5/tools: fix trace dump multiple burst completions Viacheslav Ovsiienko
2024-10-14 8:04 ` [PATCH v2 2/4] net/mlx5: fix real time counter reading from PCI BAR Viacheslav Ovsiienko
2024-10-14 8:04 ` [PATCH v2 3/4] net/mlx5: fix Tx tracing to use single clock source Viacheslav Ovsiienko
2024-10-14 8:04 ` [PATCH v2 4/4] net/mlx5: update dump script to show incomplete records Viacheslav Ovsiienko
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=20241014080434.1211629-1-viacheslavo@nvidia.com \
--to=viacheslavo@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
/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).