> The issue can cause illegal physical address access while a huge-page A
> is released and huge-page B is allocated on the same virtual address.
> The old MR can be matched using the virtual address of huge-page B but
> the HW will access the physical address of huge-page A which is no more
> part of the DPDK process.
>
> Register a driver callback for memory event in order to free out all the
> MRs of memory that is going to be freed from the dpdk process.
>
> Fixes: f8c97babc9f4 ("compress/mlx5: add data-path functions")
> Cc: sta...@dpdk.org
>
> Signed-off-by: Michael Baum <michae...@nvidia.com>
> Acked-by: Matan Azrad <ma...@nvidia.com>
> ---
> v2:
Applied to dpdk-next-crypto
Thanks.
