DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Coyle <david.coyle@intel.com>
To: akhil.goyal@nxp.com, declan.doherty@intel.com,
	pablo.de.lara.guarch@intel.com, fiona.trahe@intel.com
Cc: dev@dpdk.org, brendan.ryan@intel.com,
	mairtin.oloingsigh@intel.com, David Coyle <david.coyle@intel.com>
Subject: [dpdk-dev] [PATCH v1 0/2] enable security feature for security tests
Date: Thu, 16 Jul 2020 16:29:50 +0100	[thread overview]
Message-ID: <20200716152952.65107-1-david.coyle@intel.com> (raw)

The RTE_CRYPTODEV_FF_SECURITY feature was disabled through the
ff_disable device configuration option for all cryptodev unit tests and
crypto performance tests, including security related tests. These
patches update the crypto test tools to not disable
RTE_CRYPTODEV_FF_SECURITY for DOCSIS and PDCP security tests.

David Coyle (2):
  test/crypto: enable security feature for security tests
  app/crypto-perf: enable security feature for security tests

 app/test-crypto-perf/main.c |  7 +++++--
 app/test/test_cryptodev.c   | 22 ++++++++++++++++++----
 2 files changed, 23 insertions(+), 6 deletions(-)

-- 
2.17.1


             reply	other threads:[~2020-07-16 15:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16 15:29 David Coyle [this message]
2020-07-16 15:29 ` [dpdk-dev] [PATCH v1 1/2] test/crypto: " David Coyle
2020-07-16 17:05   ` Akhil Goyal
2020-07-18 21:18     ` Akhil Goyal
2020-07-17 18:17   ` De Lara Guarch, Pablo
2020-07-18 20:07     ` Akhil Goyal
2020-07-16 15:29 ` [dpdk-dev] [PATCH v1 2/2] app/crypto-perf: " David Coyle
2020-07-16 17:01   ` Akhil Goyal
2020-07-17 18:19   ` De Lara Guarch, Pablo
2020-07-18 20:08     ` Akhil Goyal

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=20200716152952.65107-1-david.coyle@intel.com \
    --to=david.coyle@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=brendan.ryan@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=mairtin.oloingsigh@intel.com \
    --cc=pablo.de.lara.guarch@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).