Re: [External] : [PATCH] crypto/qat: use intel-ipsec-mb for partial hash

Hello, Can I know the status of this patch, and the possible impact on any existing applications because the partial hash is switched from OpenSSL to intel-ipsec-mb which is not under FIPS certification? Thanks! Changchun From: Changchun Zhang Date: Thursday, April 14, 2022 at 2:46 PM To

Re: [External] : [PATCH] crypto/qat: use intel-ipsec-mb for partial hash

Regards, Changchun Zhang From: Fan Zhang Date: Thursday, April 7, 2022 at 11:29 AM To: dev@dpdk.org Cc: kai...@intel.com , gak...@marvell.com , pablo.de.lara.gua...@intel.com , Fan Zhang Subject: [External] : [PATCH] crypto/qat: use intel-ipsec-mb for partial hash Since openssl 3.0 now deprecates

RE: cryto_aesni_mb device data contaminated and causing crash when supporting vdev_scan/vdev_action

of the crypto session (wondering it has performance degradation). Thanks, Changchun (Alex) From: Changchun Zhang [mailto:changchun.zh...@oracle.com] Sent: Wednesday, February 2, 2022 11:08 AM To: us...@dpdk.org; dev@dpdk.org Subject: [External] : cryto_aesni_mb device data contaminated and causing

cryto_aesni_mb device data contaminated and causing crash when supporting vdev_scan/vdev_action

Hi, Has anyone noticed that crypto_aesni_mb virtual crypto device has issue of memory crash caused by the scanning and probe on secondary process. Can anyone cast any lights on it. What I encountered is: On the primary process, the crypto_aesni_mb device is probed and created successfully and I