RE: [EXTERNAL] [PATCH v3 0/2] crypto/mlx5: optimize AES-GCM IPsec operation

> To optimize AES-GCM IPsec operation within crypto/mlx5, > the DPDK API typically supplies AES_GCM AAD/Payload/Digest > in separate locations, potentially disrupting their > contiguous layout. In cases where the memory layout fails > to meet hardware (HW) requirements, an UMR WQE is initiated > ah

[PATCH v3 0/2] crypto/mlx5: optimize AES-GCM IPsec operation

To optimize AES-GCM IPsec operation within crypto/mlx5, the DPDK API typically supplies AES_GCM AAD/Payload/Digest in separate locations, potentially disrupting their contiguous layout. In cases where the memory layout fails to meet hardware (HW) requirements, an UMR WQE is initiated ahead of the G