From: Chinmaya Dwibedy <ckdwibedy@gmail.com>
To: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.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: Tue, 21 Jun 2016 12:56:08 +0530 [thread overview]
Message-ID: <CAMHS8RE1KcvLhcJvZ7df7NcD5migBg_DpEa9rDK3tpgFQ-FrJQ@mail.gmail.com> (raw)
In-Reply-To: <6e0329b1-d67c-3b23-55d2-dc88b78f6f2a@intel.com>
Hi Sergio,
As suggested by you, run ‘app/test' application and then run
'cryptodev_qat_autotest' . Found the same issue i.e., It halts in
rte_cryptodev_dequeue_burst () (while loop) in process_crypto_request ()
function (app/test/test_cryptodev.c).
Debugged the qat_crypto_pkt_rx_burst() (in drivers/crypto/qat/qat_crypto.c)
and found that , the value of resp_msg is 0x7F7F7F7F (i.e.,
ADF_RING_EMPTY_SIG) . Thus it is not getting crypto packet (i.e., rte_mbuf)
from the RX queue. But I find that, in qat_crypto_pkt_tx_burst(),
the qat_alg_write_mbuf_entry() is being called. The
qat_alg_write_mbuf_entry () prints qat_req using rte_hexdump () and
returns zero.
One question, the base_addr + tail of tx_q (in qat_crypto_pkt_tx_burst())
should be same as base_addr + head (in qat_crypto_pkt_rx_burst()). Right ?
Please feel free to correct me if I am wrong.
Also can you please provide some pointers for further debugging? Would it
be configuration issue? Note that, I am using VF in VM.
Thank you once again for your prompt response and great support.
Regards,
Chinmaya
On Mon, Jun 20, 2016 at 3:04 PM, Sergio Gonzalez Monroy <
sergio.gonzalez.monroy@intel.com> wrote:
> 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-21 7:26 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
2016-06-21 7:26 ` Chinmaya Dwibedy [this message]
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=CAMHS8RE1KcvLhcJvZ7df7NcD5migBg_DpEa9rDK3tpgFQ-FrJQ@mail.gmail.com \
--to=ckdwibedy@gmail.com \
--cc=sergio.gonzalez.monroy@intel.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).