From: Stephen Hemminger <stephen@networkplumber.org>
To: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Cc: <dev@dpdk.org>, <matan@nvidia.com>, <rasland@nvidia.com>,
<orika@nvidia.com>, <dsosnowski@nvidia.com>
Subject: Re: [PATCH 0/4] net/mlx5: series to fix and improve tx trace capabilities
Date: Wed, 9 Oct 2024 10:41:52 -0700 [thread overview]
Message-ID: <20241009104152.60bb20c8@hermes.local> (raw)
In-Reply-To: <20241009114028.973284-1-viacheslavo@nvidia.com>
On Wed, 9 Oct 2024 14:40:24 +0300
Viacheslav Ovsiienko <viacheslavo@nvidia.com> wrote:
> There is a series of weakly dependent patches related to the tx trace
> in mlx5 PMD:
> - fix issue in the trace dump Python script
> - update the real-time clock reading routine, make it atomic
> and move its initialization to the driver startup
> - advance the tx tracing in mlx5 PMD, provide real time parameter,
> read from the NIC to synchronize trace records with HW descriptors
> - update the trace dump script to see raw records and incomplete bursts
>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
>
> 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(-)
Series-Acked-by: Stephen Hemminger <stephen@networkplumber.org>
next prev parent reply other threads:[~2024-10-09 17:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 11:40 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 ` Stephen Hemminger [this message]
2024-10-14 8:04 ` [PATCH v2 0/4] net/mlx5: series to fix and improve tx trace capabilitie Viacheslav Ovsiienko
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
2024-10-22 6:37 ` [PATCH v2 0/4] net/mlx5: series to fix and improve tx trace capabilitie Raslan Darawsheh
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=20241009104152.60bb20c8@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=viacheslavo@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).