DPDK patches and discussions
 help / color / mirror / Atom feed
From: Arek Kusztal <arkadiuszx.kusztal@intel.com>
To: dev@dpdk.org
Cc: fiona.trahe@intel.com, deepak.k.jain@intel.com,
	pablo.de.lara.guarch@intel.com, john.griffin@intel.com,
	Arek Kusztal <arkadiuszx.kusztal@intel.com>
Subject: [dpdk-dev] [PATCH 0/3] add GMAC capability Intel QAT driver
Date: Thu, 25 Aug 2016 17:04:19 +0100	[thread overview]
Message-ID: <1472141062-27316-1-git-send-email-arkadiuszx.kusztal@intel.com> (raw)

This patches add AES GMAC capability to Intel(R) QuickAssist
Technology driver and corresponsing test cases.

This patchset depends on the following patches/patchsets:

"crypto/qat: enable Kasumi F9 support in QAT driver"
(http://dpdk.org/dev/patchwork/patch/15320/)

Arek Kusztal (3):
  crypto/qat: add GMAC capability to QAT crypto driver
  app/test: add GMAC authentication tests to cryptodev tests
  lib/librte_cryptodev: change GMAC API comments

 app/test/test_cryptodev.c                  | 265 +++++++++++++++++++++++++++++
 app/test/test_cryptodev_gcm_test_vectors.h | 150 ++++++++++++++++
 doc/guides/cryptodevs/qat.rst              |   1 +
 drivers/crypto/qat/qat_crypto.c            |  42 ++++-
 lib/librte_cryptodev/rte_crypto_sym.h      |  17 +-
 5 files changed, 465 insertions(+), 10 deletions(-)

-- 
2.1.0

             reply	other threads:[~2016-08-25 16:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-25 16:04 Arek Kusztal [this message]
2016-08-25 16:04 ` [dpdk-dev] [PATCH 1/3] crypto/qat: add GMAC capability to QAT crypto driver Arek Kusztal
2016-08-25 16:04 ` [dpdk-dev] [PATCH 2/3] app/test: add GMAC authentication tests to cryptodev tests Arek Kusztal
2016-08-25 16:04 ` [dpdk-dev] [PATCH 3/3] lib/librte_cryptodev: change GMAC API comments Arek Kusztal
2016-08-25 20:40 ` [dpdk-dev] [PATCH 0/3] add GMAC capability Intel QAT driver Jain, Deepak K

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=1472141062-27316-1-git-send-email-arkadiuszx.kusztal@intel.com \
    --to=arkadiuszx.kusztal@intel.com \
    --cc=deepak.k.jain@intel.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=john.griffin@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).