Dragos Tatulea 6211165448 vdpa/mlx5: Postpone MR deletion ... Currently, when a new MR is set up, the old MR is deleted. MR deletion is about 30-40% the time of MR creation. As deleting the old MR is not important for the process of setting up the new MR, this operation can be postponed. This series adds a workqueue that does MR garbage collection at a later point. If the MR lock is taken, the handler will back off and reschedule. The exception during shutdown: then the handler must not postpone the work. Note that this is only a speculative optimization: if there is some mapping operation that is triggered while the garbage collector handler has the lock taken, this operation it will have to wait for the handler to finish. Signed-off-by: Dragos Tatulea <dtatulea@nvidia.com> Reviewed-by: Cosmin Ratiu <cratiu@nvidia.com> Message-Id: <20240830105838.2666587-9-dtatulea@nvidia.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>		2024-09-25 07:07:44 -04:00
..
debug.c	vdpa/mlx5: Fix double release of debugfs entry	2023-10-18 11:29:29 -04:00
mlx5_vnet.c	vdpa/mlx5: Postpone MR deletion	2024-09-25 07:07:44 -04:00
mlx5_vnet.h	vdpa/mlx5: Re-create HW VQs under certain conditions	2024-07-09 08:42:50 -04:00