From: "Azarewicz, PiotrX T" <piotrx.t.azarewicz@intel.com>
To: "Trahe, Fiona" <fiona.trahe@intel.com>
Cc: "Mrozowicz, SlawomirX" <slawomirx.mrozowicz@intel.com>,
"Kerlin, MarcinX" <marcinx.kerlin@intel.com>,
"Mrzyglod, DanielX T" <danielx.t.mrzyglod@intel.com>,
"Mrozowicz, SlawomirX" <slawomirx.mrozowicz@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v6 3/4] app/test: added tests for libcrypto PMD
Date: Thu, 6 Oct 2016 13:53:45 +0000 [thread overview]
Message-ID: <4837007523CC9A4B9414D20C13DE6E641372AA38@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <348A99DA5F5B7549AA880327E580B435890EE063@IRSMSX101.ger.corp.intel.com>
Hi Fiona,
> This patch breaks autotests for all PMDs, due to increasing the MBUF size to
> UNIT16_MAX.
> USER1: Can't create CRYPTO_MBUFPOOL
>
> It needs more than 500MBs in the MBUFPOOL to run this test.
> Setting this back to MBUF_SIZE fixes the issue, but breaks 2 tests in
> libcrypto_autotest
>
> TestCase create_gmac_operation() line 5060 failed: no room to append aad
> + TestCase [27] : test_AES_GMAC_authentication_test_case_4 failed
> TestCase create_gmac_operation() line 5060 failed: no room to append aad
> + TestCase [28] : test_AES_GMAC_authentication_verify_test_case_4 failed
>
> Can you investigate if it's possible to run these 2 tests using a different
> smaller MBUFPOOL - maybe with only a few large mbufs?
Yes, I think that it is possible to run these 2 tests using a different mempoll.
I will make a fix for the issue.
Piotr
next prev parent reply other threads:[~2016-10-06 13:53 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 8:59 [dpdk-dev] [PATCH v2 0/4] new crypto software based device Michal Jastrzebski
2016-09-19 8:59 ` [dpdk-dev] [PATCH v2 1/4] libcrypto_pmd: initial implementation of SW crypto device Michal Jastrzebski
2016-09-19 8:59 ` [dpdk-dev] [PATCH v2 2/4] lib/cryptodev: added support to libcrypto PMD Michal Jastrzebski
2016-09-19 22:59 ` De Lara Guarch, Pablo
2016-09-19 8:59 ` [dpdk-dev] [PATCH v2 3/4] app/test: added tests for " Michal Jastrzebski
2016-09-19 8:59 ` [dpdk-dev] [PATCH v2 4/4] examples/l2fwd-crypto: updated example " Michal Jastrzebski
2016-09-19 23:58 ` De Lara Guarch, Pablo
2016-09-29 14:14 ` [dpdk-dev] [PATCH v3 0/3] new crypto software based device Slawomir Mrozowicz
2016-09-29 14:14 ` [dpdk-dev] [PATCH v3 1/3] libcrypto_pmd: initial implementation of SW crypto device Slawomir Mrozowicz
2016-09-29 14:14 ` [dpdk-dev] [PATCH v3 2/3] app/test: added tests for libcrypto PMD Slawomir Mrozowicz
2016-09-29 14:39 ` [dpdk-dev] [PATCH v3 3/3] examples/l2fwd-crypto: updated example " Slawomir Mrozowicz
2016-09-30 16:17 ` [dpdk-dev] [PATCH v4 0/5] new crypto software based device Slawomir Mrozowicz
2016-09-30 16:17 ` [dpdk-dev] [PATCH v4 1/5] libcrypto_pmd: initial implementation of SW crypto device Slawomir Mrozowicz
2016-09-30 16:32 ` [dpdk-dev] [PATCH v4 2/5] app/test: cryptodev AES tests rework Slawomir Mrozowicz
2016-09-30 16:32 ` [dpdk-dev] [PATCH v4 3/5] app/test: added tests for libcrypto PMD Slawomir Mrozowicz
2016-09-30 16:32 ` [dpdk-dev] [PATCH v4 4/5] app/test: added big data GMAC test for libcrypto Slawomir Mrozowicz
2016-09-30 17:18 ` Thomas Monjalon
2016-10-03 8:12 ` Mrozowicz, SlawomirX
2016-09-30 16:32 ` [dpdk-dev] [PATCH v4 5/5] examples/l2fwd-crypto: updated example for libcrypto PMD Slawomir Mrozowicz
2016-10-03 14:26 ` [dpdk-dev] [PATCH v5 0/4] new crypto software based device Slawomir Mrozowicz
2016-10-03 14:45 ` [dpdk-dev] [PATCH v5 1/4] libcrypto_pmd: initial implementation of SW crypto device Slawomir Mrozowicz
2016-10-03 15:02 ` [dpdk-dev] [PATCH v5 2/4] app/test: cryptodev AES tests rework Slawomir Mrozowicz
2016-10-03 15:17 ` [dpdk-dev] [PATCH v5 3/4] app/test: added tests for libcrypto PMD Slawomir Mrozowicz
2016-10-03 15:28 ` [dpdk-dev] [PATCH v5 4/4] examples/l2fwd-crypto: updated example " Slawomir Mrozowicz
2016-10-03 22:36 ` [dpdk-dev] [PATCH v5 0/4] new crypto software based device De Lara Guarch, Pablo
2016-10-04 15:11 ` [dpdk-dev] [PATCH v6 " Slawomir Mrozowicz
2016-10-04 15:11 ` [dpdk-dev] [PATCH v6 1/4] libcrypto_pmd: initial implementation of SW crypto device Slawomir Mrozowicz
2016-10-04 15:11 ` [dpdk-dev] [PATCH v6 2/4] app/test: cryptodev AES tests rework Slawomir Mrozowicz
2016-10-04 15:11 ` [dpdk-dev] [PATCH v6 3/4] app/test: added tests for libcrypto PMD Slawomir Mrozowicz
2016-10-06 13:30 ` Trahe, Fiona
2016-10-06 13:53 ` Azarewicz, PiotrX T [this message]
2016-10-04 15:11 ` [dpdk-dev] [PATCH v6 4/4] examples/l2fwd-crypto: updated example " Slawomir Mrozowicz
2016-10-04 23:36 ` [dpdk-dev] [PATCH v6 0/4] new crypto software based device De Lara Guarch, Pablo
2016-10-05 0:05 ` De Lara Guarch, Pablo
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=4837007523CC9A4B9414D20C13DE6E641372AA38@IRSMSX102.ger.corp.intel.com \
--to=piotrx.t.azarewicz@intel.com \
--cc=danielx.t.mrzyglod@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=marcinx.kerlin@intel.com \
--cc=slawomirx.mrozowicz@intel.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).