[dpdk-dev] example/l2fwd-crypto: maybe an issue?
declan.doherty at intel.com
Mon Jun 27 10:44:48 CEST 2016
On 23/06/16 06:30, Xuelin Shi wrote:
> Do we have assumption each core will have a separate crypto device?
> I have only one crypto device with several queues which are shared by multi-cores.
> As I run the l2fwd-crypto, only one cparam is valid and has a good dev_id.
> The other cparam is crashing.
> The reason is the other qconf assoicated with the core is not initializing the dev_id
> since only one crypto device is available.
Hey Forrest, yes we made the assumption of one device per core the
application, we just default to using queue pair 0 of each crypto
device. It shouldn't be to much work to modify the main() and
initialize_cryptodevs() to instead allocate a cryptodev and queue pair
to each set of cparams. If you are using software crypto PMDs such as
the AESNI_MB PMD the simplest approach is just to create multiple
devices using the EAL options.
More information about the dev