diff options
| author | Dragos Tatulea <dtatulea@nvidia.com> | 2024-06-26 13:26:59 +0300 |
|---|---|---|
| committer | Michael S. Tsirkin <mst@redhat.com> | 2024-07-09 08:42:50 -0400 |
| commit | 2638134f710364c9e696a155bf16c6847959b1d9 (patch) | |
| tree | bf79c317bdcf8e8ab74e89fd7902f247f87fa69a /tools/perf/scripts/python/gecko.py | |
| 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 <cratiu@nvidia.com>
Acked-by: Eugenio Pérez <eperezma@redhat.com>
Signed-off-by: Dragos Tatulea <dtatulea@nvidia.com>
Message-Id: <20240626-stage-vdpa-vq-precreate-v2-23-560c491078df@nvidia.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/gecko.py')
0 files changed, 0 insertions, 0 deletions