patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Ruifeng Wang <ruifeng.wang@arm.com>,
	"pablo.de.lara.guarch@intel.com" <pablo.de.lara.guarch@intel.com>,
	"declan.doherty@intel.com" <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"roy.fan.zhang@intel.com" <roy.fan.zhang@intel.com>,
	"gavin.hu@arm.com" <gavin.hu@arm.com>,
	"honnappa.nagarahalli@arm.com" <honnappa.nagarahalli@arm.com>,
	"nd@arm.com" <nd@arm.com>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] test/crypto: fix unit test failure for virtual	cryptodev
Date: Thu, 19 Sep 2019 15:11:08 +0000	[thread overview]
Message-ID: <DB8PR04MB66355C38B8F19659B9A0F494E6890@DB8PR04MB6635.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20190905081044.1154-1-ruifeng.wang@arm.com>

> 
> armv8 cryptodev virtual PMD autotest failed with output:
> CRYPTODEV: [CRYPTODEV_NAME_ARMV8_CRYPTO_PMD]
> armv8_crypto_pmd_qp_create_processed_ops_ring() line 210:
> Unable to reuse existing ring armv8_crypto_pmd_0_qp_0 for processed ops
> CRYPTODEV: rte_cryptodev_stop() line 942:
> Device with dev_id=0 already stopped
> + TestCase [ 0] : test_AES_chain_armv8_all failed
> 
> This is due to the ring size used in ut_setup is bigger than that used
> in testsuite_setup.
> Fix this issue by enlarge ring size used in testsuite_setup accordingly.
> 
> Fixes: 24054e3640a2 ("test/crypto: use separate session mempools")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Ruifeng Wang <ruifeng.wang@arm.com>
> Reviewed-by: Gavin Hu <gavin.hu@arm.com>
> ---
Applied to dpdk-next-crypto

Thanks.


      reply	other threads:[~2019-09-19 15:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-05  8:10 [dpdk-stable] " Ruifeng Wang
2019-09-19 15:11 ` Akhil Goyal [this message]

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=DB8PR04MB66355C38B8F19659B9A0F494E6890@DB8PR04MB6635.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=gavin.hu@arm.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=nd@arm.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=roy.fan.zhang@intel.com \
    --cc=ruifeng.wang@arm.com \
    --cc=stable@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).