|
Revision tags: v24.11, v24.11-rc4, v24.11-rc3, v24.11-rc2, v24.11-rc1 |
|
| #
171360df |
| 14-Oct-2024 |
Viacheslav Ovsiienko <viacheslavo@nvidia.com> |
net/mlx5: show incomplete records in Tx trace script
If the trace dump is stored at the moment when there is some incomplete Tx transfers - WQE is pushed but hardware did not sent the completions ye
net/mlx5: show incomplete records in Tx trace script
If the trace dump is stored at the moment when there is some incomplete Tx transfers - WQE is pushed but hardware did not sent the completions yet - this incomplete was not dumped by the script mlx5_trace. For some cases (for example, if queue was stuck) the valuable debug information was lost.
To improve the dump fullness the following optional script arguments are added:
-v [level] - provides the raw dump of the object record of the specified level (0 - bursts, 1 - WQEs, 2+ - mbufs) -a - dumps all bursts, including incomplete ones
Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com> Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
show more ...
|
| #
02932480 |
| 14-Oct-2024 |
Tim Martin <timothym@nvidia.com> |
net/mlx5: fix Tx tracing to use single clock source
A prior commit introduced tracing for mlx5, but there is a mixture of two unrelated clocks used: the TSC for host work submission timestamps and t
net/mlx5: fix Tx tracing to use single clock source
A prior commit introduced tracing for mlx5, but there is a mixture of two unrelated clocks used: the TSC for host work submission timestamps and the NIC HW clock for CQE completion times. It is necessary to have timestamps from a single common clock, and the NIC HW clock is the better choice since it can be used with externally synchronized clocks.
This patch adds the NIC HW clock as an additional logged parameter for trace_tx_entry, trace_tx_exit, and trace_tx_wqe. The included trace analysis python script is also updated to use the new clock when it is available.
Fixes: a1e910f5b8d4 ("net/mlx5: introduce tracepoints") Fixes: 9725191a7e14 ("net/mlx5: add Tx datapath trace analyzing script") Cc: stable@dpdk.org
Signed-off-by: Tim Martin <timothym@nvidia.com> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
show more ...
|
| #
d6721527 |
| 14-Oct-2024 |
Viacheslav Ovsiienko <viacheslavo@nvidia.com> |
net/mlx5: fix trace script for multiple burst completion
In case if there were multiple bursts completed in the single completion the first only burst was moved to the done list. The situation is no
net/mlx5: fix trace script for multiple burst completion
In case if there were multiple bursts completed in the single completion the first only burst was moved to the done list. The situation is not typical, because usually tracing was used for scheduled traffic debugging and for this case each burst had its own completion requested, and there were no completions with multiple bursts.
Fixes: 9725191a7e14 ("net/mlx5: add Tx datapath trace analyzing script") Cc: stable@dpdk.org
Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com> Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
show more ...
|
|
Revision tags: v24.07, v24.07-rc4, v24.07-rc3, v24.07-rc2, v24.07-rc1, v24.03, v24.03-rc4, v24.03-rc3, v24.03-rc2, v24.03-rc1, v23.11, v23.11-rc4, v23.11-rc3, v23.11-rc2, v23.11-rc1, v23.07, v23.07-rc4, v23.07-rc3 |
|
| #
9725191a |
| 11-Jul-2023 |
Viacheslav Ovsiienko <viacheslavo@nvidia.com> |
net/mlx5: add Tx datapath trace analyzing script
The Python script is intended to analyze mlx5 PMD datapath traces and report: - tx_burst routine timings - how packets are pushed to WQEs - how
net/mlx5: add Tx datapath trace analyzing script
The Python script is intended to analyze mlx5 PMD datapath traces and report: - tx_burst routine timings - how packets are pushed to WQEs - how packet sending is completed with timings
Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
show more ...
|