Hi Akhil,
-----Original Message-----
From: Akhil Goyal <akhil.go...@nxp.com>
Sent: Wednesday, April 15, 2020 8:20 PM
To: Medvedkin, Vladimir <vladimir.medved...@intel.com>; dev@dpdk.org
Cc: Ananyev, Konstantin <konstantin.anan...@intel.com>
Subject: RE: [PATCH v2] examples/ipsec-secgw: remove limitation for crypto
sessions
Hi Vladimir,
>
> Get rid of hardcoded limit of cryptodev sessions.
>
> Fixes: e1143d7dbbf4 ("examples/ipsec-secgw: get rid of maximum SA
> limitation")
> Cc: vladimir.medved...@intel.com
>
> Signed-off-by: Vladimir Medvedkin <vladimir.medved...@intel.com>
> ---
This will create an issue in case of rte_security sessions.
Rte_security session create APIs were not updated when the provision for having
Separate mempools for session and session private data was introduced.
As a result the number of entries in session_priv_pool should be double the
number of Supported sessions - one for session and one for session priv data.
This should be fixed in rte_security API but this would mean an API breakage
which cannot Be done before 20.11. So this patch need to be deferred till it is
not fixed in rte_security.
Or we can have double the number of required entries in mempool.
I will double the number entries in mempool. Thanks!
Regards,
Akhil
