c5ae1954c4
To prevent a hardware memory leak when a DEVX DCT object is destroyed
without calling DRAIN DCT before, (e.g. under cleanup flow), need to
manage its creation and destruction via mlx5 core.
In that case the DRAIN DCT command will be called and only once that it
will be completed the DESTROY DCT command will be called. Otherwise, the
DESTROY DCT may fail and a hardware leak may occur.
As of that change the DRAIN DCT command should not be exposed any more
from DEVX, it's managed internally by the driver to work as expected by
the device specification.
Fixes:
|
||
|---|---|---|
| .. | ||
| mlx4 | ||
| mlx5/core | ||
| mlxfw | ||
| mlxsw | ||
| Kconfig | ||
| Makefile | ||