crypto: qat - fix apply custom thread-service mapping for dc service
authorShashank Gupta <shashank.gupta@intel.com>
Mon, 6 Mar 2023 16:09:23 +0000 (11:09 -0500)
committerHerbert Xu <herbert@gondor.apana.org.au>
Fri, 17 Mar 2023 03:09:19 +0000 (11:09 +0800)
commit118dbccc1a35b50bf41296846809487e914b65a1
treec92724ede3995f70d2ef3b146da7ac7008762324
parenta3e8c919b9930e31b705ec7b2f898a59e213a393
crypto: qat - fix apply custom thread-service mapping for dc service

The thread to arbiter mapping for 4xxx devices does not allow to
achieve optimal performance for the compression service as it makes
all the engines to compete for the same resources.

Update the logic so that a custom optimal mapping is used for the
compression service.

Signed-off-by: Shashank Gupta <shashank.gupta@intel.com>
Reviewed-by: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
drivers/crypto/qat/qat_4xxx/adf_4xxx_hw_data.c
drivers/crypto/qat/qat_c3xxx/adf_c3xxx_hw_data.c
drivers/crypto/qat/qat_c62x/adf_c62x_hw_data.c
drivers/crypto/qat/qat_common/adf_accel_devices.h
drivers/crypto/qat/qat_common/adf_hw_arbiter.c
drivers/crypto/qat/qat_dh895xcc/adf_dh895xcc_hw_data.c