From: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
To: Chinmaya Dwibedy <ckdwibedy@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Issue with ipsec-secgw sample application on VM using Intel QAT device (pass-through mode)
Date: Mon, 20 Jun 2016 10:34:57 +0100 [thread overview]
Message-ID: <6e0329b1-d67c-3b23-55d2-dc88b78f6f2a@intel.com> (raw)
In-Reply-To: <CAMHS8RHNFBem6eFV5MNibv5=W8F3yH4gnuuBBswE11Fnb=vaYA@mail.gmail.com>
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
next prev parent reply other threads:[~2016-06-20 9:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 12:01 Chinmaya Dwibedy
2016-06-15 12:35 ` Sergio Gonzalez Monroy
2016-06-20 7:33 ` Chinmaya Dwibedy
2016-06-20 8:06 ` Sergio Gonzalez Monroy
2016-06-20 9:08 ` Chinmaya Dwibedy
2016-06-20 9:34 ` Sergio Gonzalez Monroy [this message]
2016-06-21 7:26 ` Chinmaya Dwibedy
2016-06-21 15:40 ` Sergio Gonzalez Monroy
2016-06-22 8:09 ` Chinmaya Dwibedy
2016-06-23 11:48 ` Chinmaya Dwibedy
2016-06-24 9:34 ` Chinmaya Dwibedy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6e0329b1-d67c-3b23-55d2-dc88b78f6f2a@intel.com \
--to=sergio.gonzalez.monroy@intel.com \
--cc=ckdwibedy@gmail.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).