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, pablo.de.lara.guarch@intel.com,
	john.griffin@intel.com, deepak.k.jain@intel.com,
	Arek Kusztal <arkadiuszx.kusztal@intel.com>
Subject: [dpdk-dev] [PATCH 0/3] Add scatter-gather list capability to Intel QuickAssist Technology driver
Date: Wed, 30 Nov 2016 15:52:12 +0000	[thread overview]
Message-ID: <1480521135-14869-1-git-send-email-arkadiuszx.kusztal@intel.com> (raw)

This patchset adds scatter-gather list (SGL) capability to Intel QuickAssist Technology driver
and corresponding tests to QAT cryptodev test suite.

This patchset depends on the following patches/patchsets:

"crypto/qat: fix to avoid buffer overwrite in OOP case"
(http://dpdk.org/dev/patchwork/patch/17241)

Arek Kusztal (3):
  lib/librte_cryptodev: add private member to crypto op struct
  crypto/qat: add SGL capability to Intel QuickAssist driver
  app/test: add SGL tests to cryptodev QAT suite

 app/test/test_cryptodev.c                  | 356 +++++++++++++
 app/test/test_cryptodev_gcm_test_vectors.h | 823 ++++++++++++++++++++++++++++-
 doc/guides/rel_notes/release_17_02.rst     |   5 +
 drivers/crypto/qat/qat_crypto.c            | 145 ++++-
 drivers/crypto/qat/qat_crypto.h            |   6 +
 drivers/crypto/qat/qat_qp.c                |  28 +
 lib/librte_cryptodev/rte_crypto.h          |   4 +
 7 files changed, 1353 insertions(+), 14 deletions(-)

-- 
2.1.0

             reply	other threads:[~2016-11-30 15:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30 15:52 Arek Kusztal [this message]
2016-11-30 15:52 ` [dpdk-dev] [PATCH 1/3] lib/librte_cryptodev: add private member to crypto op struct Arek Kusztal
2016-11-30 15:52 ` [dpdk-dev] [PATCH 2/3] crypto/qat: add SGL capability to Intel QuickAssist driver Arek Kusztal
2016-11-30 15:52 ` [dpdk-dev] [PATCH 3/3] app/test: add SGL tests to cryptodev QAT suite Arek Kusztal

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=1480521135-14869-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).