Hi Kai,
Please review.
> From: Julien Hascoet <ju.hasc...@gmail.com>
>
> The crypto scheduler session size computation was taking
> into account only the worker session sizes and not its own.
>
> Fixes: e2af4e403c1 ("crypto/scheduler: support DOCSIS security protocol")
> Cc: sta...@dpdk.org
>
> Signed-off-by: Julien Hascoet <ju.hasc...@gmail.com>
> ---
> drivers/crypto/scheduler/scheduler_pmd_ops.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/crypto/scheduler/scheduler_pmd_ops.c
> b/drivers/crypto/scheduler/scheduler_pmd_ops.c
> index a18f7a08b0..6e43438469 100644
> --- a/drivers/crypto/scheduler/scheduler_pmd_ops.c
> +++ b/drivers/crypto/scheduler/scheduler_pmd_ops.c
> @@ -185,7 +185,7 @@ scheduler_session_size_get(struct scheduler_ctx
> *sched_ctx,
> uint8_t session_type)
> {
> uint8_t i = 0;
> - uint32_t max_priv_sess_size = 0;
> + uint32_t max_priv_sess_size = sizeof(struct scheduler_session_ctx);
>
> /* Check what is the maximum private session size for all workers */
> for (i = 0; i < sched_ctx->nb_workers; i++) {
