diff options
author | Hamdan Igbaria <hamdani@nvidia.com> | 2023-11-16 14:51:01 +0300 |
---|---|---|
committer | Saeed Mahameed <saeedm@nvidia.com> | 2024-02-06 03:45:53 +0300 |
commit | 917d1e799ddf9492bd0c71a23d84af0b6bb12bae (patch) | |
tree | ff89a91385ec85da1941717cb7486f504780d868 /tools/perf/scripts/python/export-to-sqlite.py | |
parent | 507472ed0e37244e7703378409407b0606de6077 (diff) | |
download | linux-917d1e799ddf9492bd0c71a23d84af0b6bb12bae.tar.xz |
net/mlx5: DR, Change SWS usage to debug fs seq_file interface
In current SWS debug dump mechanism we implement the seq_file interface,
but we only implement the 'show' callback to dump the whole steering DB
with a single call to this callback.
However, for large data size the seq_printf function will fail to
allocate a buffer with the adequate capacity to hold such data.
This patch solves this problem by utilizing the seq_file interface
mechanism in the following way:
- when the user triggers a dump procedure, we will allocate a list of
buffers that hold the whole data dump (in the start callback)
- using the start, next, show and stop callbacks of the seq_file
API we iterate through the list and dump the whole data
Signed-off-by: Hamdan Igbaria <hamdani@nvidia.com>
Reviewed-by: Yevgeny Kliteynik <kliteyn@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