> Currently the performance application creates a device session per lcore.
> This was not reflected in how many session objects were available
> in the mempool, when using a scheduler device.
> 
> The number of lcores is now taken into consideration when calculating
> how many sessions are needed for the scheduler.
> 
> Fixes: 09fcf99dcad2 ("test/crypto-perf: fix number of scheduler sessions")
> 
> Reported-by: Kevin O'Sullivan <kevin.osulli...@intel.com>
> Signed-off-by: Ciara Power <ciara.po...@intel.com>
Series applied to dpdk-next-crypto

Thanks.

Reply via email to