DPDK patches and discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Trahe, Fiona" <fiona.trahe@intel.com>,
	"Griffin, John" <john.griffin@intel.com>,
	"Jain, Deepak K" <deepak.k.jain@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/3] performance enhancements for QAT driver
Date: Mon, 18 Sep 2017 11:03:25 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CC1E829@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <cover.1505142402.git.anatoly.burakov@intel.com>



> -----Original Message-----
> From: Burakov, Anatoly
> Sent: Tuesday, September 12, 2017 10:31 AM
> To: dev@dpdk.org
> Cc: Trahe, Fiona <fiona.trahe@intel.com>; Griffin, John
> <john.griffin@intel.com>; Jain, Deepak K <deepak.k.jain@intel.com>; De
> Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> Subject: [PATCH v2 0/3] performance enhancements for QAT driver
> 
> A few performance enhancements for QAT crypto driver. These include:
> - Removing reliance on atomics on hot path
>   - This adds a new limitation, making queue pairs single-threaded
> - Coalesce RX and TX CSR writes
> 
> v2: added cover letter
>     fixed commit messages
>     fixed documentation
> 
> Anatoly Burakov (3):
>   crypto/qat: remove atomics
>   crypto/qat: enable RX head writes coalescing
>   crypto/qat: enable TX tail writes coalescing
> 
>  doc/guides/cryptodevs/qat.rst          |  1 +
>  doc/guides/rel_notes/release_17_11.rst |  8 ++++
>  drivers/crypto/qat/qat_crypto.c        | 84 +++++++++++++++++++++++++-
> --------
>  drivers/crypto/qat/qat_crypto.h        | 15 +++++-
>  drivers/crypto/qat/qat_qp.c            |  4 +-
>  5 files changed, 88 insertions(+), 24 deletions(-)
> 
> --
> 2.7.4

Applied to dpdk-next-crypto.
Thanks,

Pablo

  parent reply	other threads:[~2017-09-18 11:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1503651900.git.anatoly.burakov@intel.com>
2017-08-25  9:30 ` [dpdk-dev] [DPDK] [PATCH 1/3] qat: remove atomics Anatoly Burakov
2017-09-04 14:39   ` De Lara Guarch, Pablo
2017-09-12  9:31   ` [dpdk-dev] [PATCH v2 0/3] performance enhancements for QAT driver Anatoly Burakov
2017-09-12  9:31     ` [dpdk-dev] [PATCH v2 1/3] crypto/qat: remove atomics Anatoly Burakov
2017-09-15 11:35       ` Trahe, Fiona
2017-09-12  9:31     ` [dpdk-dev] [PATCH v2 2/3] crypto/qat: enable RX head writes coalescing Anatoly Burakov
2017-09-15 11:55       ` Trahe, Fiona
2017-09-12  9:31     ` [dpdk-dev] [PATCH v2 3/3] crypto/qat: enable TX tail " Anatoly Burakov
2017-09-15 13:17       ` Trahe, Fiona
2017-09-18 11:03     ` De Lara Guarch, Pablo [this message]
2017-08-25  9:30 ` [dpdk-dev] [DPDK] [PATCH 2/3] qat: enable RX head " Anatoly Burakov
2017-08-25  9:30 ` [dpdk-dev] [DPDK] [PATCH 3/3] qat: enable TX tail " Anatoly Burakov

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=E115CCD9D858EF4F90C690B0DCB4D8976CC1E829@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=deepak.k.jain@intel.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=john.griffin@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).