From: Jerin Jacob <jerinjacobk@gmail.com>
To: "Gujjar, Abhinandan S" <abhinandan.gujjar@intel.com>
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"jerinj@marvell.com" <jerinj@marvell.com>
Subject: Re: [dpdk-dev] [PATCH 1/6] test/event_crypto: fix missing IV value for AES algo
Date: Wed, 16 Oct 2019 13:31:26 +0530 [thread overview]
Message-ID: <CALBAE1NaUoSam-J8enGWA5KOZy9BYKJ4RG3LuRsMUUonCaqPkw@mail.gmail.com> (raw)
In-Reply-To: <5612CB344B05EE4F95FC5B729939F7807954E11C@PGSMSX102.gar.corp.intel.com>
On Fri, Oct 4, 2019 at 3:05 PM Gujjar, Abhinandan S
<abhinandan.gujjar@intel.com> wrote:
>
> Hi Hemanth,
>
> I tried to test the series of patches on test with SW adapter.
> Looks like, test hangs after 3rd case!
> Not sure, if I am missing any params to be passed to the app or anything else has to be done.
Waiting for your reply to review further and apply to the
next-eventdev tree(after getting the ack from Abhinandan)
>
> + ------------------------------------------------------- +
> + TestCase [ 0] : test_crypto_adapter_create succeeded
> + TestCase [ 1] : test_crypto_adapter_qp_add_del succeeded
> +------------------------------------------------------+
> + Crypto adapter stats for instance 0:
> + Event port poll count 0
> + Event dequeue count 0
> + Cryptodev enqueue count 0
> + Cryptodev enqueue failed count 0
> + Cryptodev dequeue count 0
> + Event enqueue count 0
> + Event enqueue retry count 0
> + Event enqueue fail count 0
> +------------------------------------------------------+
> + TestCase [ 2] : test_crypto_adapter_stats succeeded
>
next prev parent reply other threads:[~2019-10-16 8:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 11:33 Hemant Agrawal
2019-10-01 11:33 ` [dpdk-dev] [PATCH 2/6] test/event_crypto: fix check for HW support Hemant Agrawal
2019-10-01 11:33 ` [dpdk-dev] [PATCH 3/6] test/event_crypto: fix to avail the mempool entries Hemant Agrawal
2019-10-01 11:33 ` [dpdk-dev] [PATCH 4/6] test/event_crypto: support to release the atomic ctxt Hemant Agrawal
2019-10-01 11:33 ` [dpdk-dev] [PATCH 5/6] test/event_crypto: use device cap instead of fixed values Hemant Agrawal
2019-10-01 11:33 ` [dpdk-dev] [PATCH 6/6] test/event_crypto: separate the NEW and FWD mode inits Hemant Agrawal
2019-10-03 3:24 ` [dpdk-dev] [PATCH 1/6] test/event_crypto: fix missing IV value for AES algo Jerin Jacob
2019-10-03 4:52 ` Gujjar, Abhinandan S
2019-10-04 9:35 ` Gujjar, Abhinandan S
2019-10-16 8:01 ` Jerin Jacob [this message]
2019-10-18 5:28 ` Hemant Agrawal
2019-11-07 9:01 ` [dpdk-dev] [PATCH v2 1/3] " Hemant Agrawal
2019-11-07 9:01 ` [dpdk-dev] [PATCH v2 2/3] test/event_crypto: fix to avail the mempool entries Hemant Agrawal
2019-11-07 9:01 ` [dpdk-dev] [PATCH v2 3/3] test/event_crypto: fix check for HW support Hemant Agrawal
2019-11-18 15:59 ` [dpdk-dev] [PATCH v2 1/3] test/event_crypto: fix missing IV value for AES algo Jerin Jacob
2019-11-18 16:02 ` Gujjar, Abhinandan S
2019-11-19 10:36 ` Gujjar, Abhinandan S
2019-11-20 13:39 ` Jerin Jacob
2019-11-26 5:55 ` Jerin Jacob
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=CALBAE1NaUoSam-J8enGWA5KOZy9BYKJ4RG3LuRsMUUonCaqPkw@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=abhinandan.gujjar@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
/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).