DPDK patches and discussions
 help / color / mirror / Atom feed
From: Fiona Trahe <fiona.trahe@intel.com>
To: dev@dpdk.org
Cc: pablo.de.lara.guarch@intel.com, fiona.trahe@intel.com,
	john.griffin@intel.com, deepak.k.jain@intel.com,
	arkadiuszx.kusztal@intel.com
Subject: [dpdk-dev] [PATCH 0/2] crypto/qat: performance optimisation
Date: Mon, 24 Oct 2016 12:59:58 +0100	[thread overview]
Message-ID: <1477310400-4934-1-git-send-email-fiona.trahe@intel.com> (raw)

QAT PMD adjusts the buffer start address and offsets passed
to the device so that the DMAs in and out of the device are
64-byte aligned.
This gives more consistent throughput, which had been
variable depending on how the application set up the mbuf.
The message builder code had to be considerably re-factored
to do this efficiently.
Also performance test not taking IV prepend offsets 
into account were corrected.

Fiona Trahe (2):
  crypto/qat: rework request builder for performance
  app/test: use correct offsets in AES perf test

 app/test/test_cryptodev_perf.c                   |  15 +-
 drivers/crypto/qat/qat_adf/icp_qat_hw.h          |   5 +
 drivers/crypto/qat/qat_adf/qat_algs.h            |   1 +
 drivers/crypto/qat/qat_adf/qat_algs_build_desc.c |   2 +
 drivers/crypto/qat/qat_crypto.c                  | 242 ++++++++++++++++-------
 5 files changed, 185 insertions(+), 80 deletions(-)

-- 
2.5.0

             reply	other threads:[~2016-10-24 12:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-24 11:59 Fiona Trahe [this message]
2016-10-24 11:59 ` [dpdk-dev] [PATCH 1/2] crypto/qat: rework request builder for performance Fiona Trahe
2016-10-24 13:34   ` Jain, Deepak K
2016-10-24 12:00 ` [dpdk-dev] [PATCH 2/2] app/test: use correct offsets in AES perf test Fiona Trahe
2016-10-24 13:35   ` Jain, Deepak K
2016-10-25 14:45 ` [dpdk-dev] [PATCH 0/2] crypto/qat: performance optimisation 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=1477310400-4934-1-git-send-email-fiona.trahe@intel.com \
    --to=fiona.trahe@intel.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=deepak.k.jain@intel.com \
    --cc=dev@dpdk.org \
    --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).