On 20/06/2016 10:08, Chinmaya Dwibedy wrote: > > Hi Sergio, > > > Agreed. We might not dequeue the same amount of crypto ops we just > previously enqueued, it's asynchronous. But in this case, I have sent > just one UDP packet. So there will be one crypto ops. Right? Also I > put a sleep (50) after the rte_crypto_enqueue_burst() function in > ipsec_processing() (ipsec.c) , so as to allow more time ( for QAT > device) for processing. Still getting the same result i.e., the > rte_crypto_dequeue_burst () functionreturns zero. > > > In case of S/W crypto device (i.e., AESNI), the VM gets inbound UDP > packets on Port 1/eth1, encapsulates (after consulting its SPD) in an > IPsec ESP packet and sends to its peer through Port 0/eth0 interface. > > > Yes, the security policy, security association and Routing > entries/configurations are exactly same. Please feel free to let me > know if you need additional information. >
Could you try to run 'app/test' application then run 'cryptodev_qat_autotest' ? That is a functional test for cryptodev QAT PMD. Sergio
