diff options
| author | Dragos Tatulea <[email protected]> | 2024-06-26 13:26:59 +0300 |
|---|---|---|
| committer | Michael S. Tsirkin <[email protected]> | 2024-07-09 08:42:50 -0400 |
| commit | 2638134f710364c9e696a155bf16c6847959b1d9 (patch) | |
| tree | bf79c317bdcf8e8ab74e89fd7902f247f87fa69a /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 0fe963d6fc162cd8c9b6c82205ea62e69088c063 (diff) | |
vdpa/mlx5: Don't reset VQs more than necessary
The vdpa device can be reset many times in sequence without any
significant state changes in between. Previously this was not a problem:
VQs were torn down only on first reset. But after VQ pre-creation was
introduced, each reset will delete and re-create the hardware VQs and
their associated resources.
To solve this problem, avoid resetting hardware VQs if the VQs are still
in a blank state.
Reviewed-by: Cosmin Ratiu <[email protected]>
Acked-by: Eugenio Pérez <[email protected]>
Signed-off-by: Dragos Tatulea <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions