summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-sqlite.py
diff options
context:
space:
mode:
authorYevgeny Kliteynik <kliteyn@nvidia.com>2022-11-15 01:33:25 +0300
committerSaeed Mahameed <saeedm@nvidia.com>2023-04-15 01:06:21 +0300
commit7d7c9453d679fe55d72d63bacb3b639cd963ebc0 (patch)
treeede0f0d083bdbb947d4b95c68f5052dd5458cf8e /tools/perf/scripts/python/export-to-sqlite.py
parent4605fc0a2b652070f45b0a17967c2cb11a9e5a6e (diff)
downloadlinux-7d7c9453d679fe55d72d63bacb3b639cd963ebc0.tar.xz
net/mlx5: DR, Read ICM memory into dedicated buffer
Instead of using the write buffer for reading we will use a dedicated buffer only for reading ICM memory. Due to the new support for args, we can have a case with pending_wc being odd number, and with reading into the same write buffer, it is possible to overwrite next write on the same slot. For example: pending_wc is 17 so the buffer for write is: | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | and we have requests as follows: r wr wr wr wr wr wr wr wr Now, the first read will be written into the last write because we use the same buffer for read and write, before it was written to the HW and we will have a wrong data in the ICM area. Signed-off-by: Erez Shitrit <erezsh@nvidia.com> Signed-off-by: Yevgeny Kliteynik <kliteyn@nvidia.com> Reviewed-by: Alex Vesker <valex@nvidia.com> Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions