Hi Akhil,

-----Original Message-----
From: Akhil Goyal <[email protected]> 
Sent: Wednesday, April 15, 2020 8:20 PM
To: Medvedkin, Vladimir <[email protected]>; [email protected]
Cc: Ananyev, Konstantin <[email protected]>
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: [email protected]
> 
> Signed-off-by: Vladimir Medvedkin <[email protected]>
> ---
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

Reply via email to