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: "Griffin, John" <john.griffin@intel.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>,
"Jain, Deepak K" <deepak.k.jain@intel.com>
Subject: Re: [dpdk-dev] [DPDK] [PATCH 1/3] qat: remove atomics
Date: Mon, 4 Sep 2017 14:39:56 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CC154EB@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <7ebf9384e20ea6fde085044c505e19719d041d25.1503651900.git.anatoly.burakov@intel.com>
> -----Original Message-----
> From: Burakov, Anatoly
> Sent: Friday, August 25, 2017 10:31 AM
> To: dev@dpdk.org
> Cc: Griffin, John <john.griffin@intel.com>; Trahe, Fiona
> <fiona.trahe@intel.com>; Jain, Deepak K <deepak.k.jain@intel.com>; De
> Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Burakov, Anatoly
> <anatoly.burakov@intel.com>
> Subject: [DPDK] [PATCH 1/3] qat: remove atomics
Title should be "crypto/qat: remove..."
>
> From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
>
> Replacing atomics in the qat driver with simple 16-bit integers for number
> of inflight packets.
>
> This adds a new limitation to the QAT driver: each queue pair is now
> explicitly single-threaded.
>
> Signed-off-by: Burakov, Anatoly <anatoly.burakov@intel.com>
> ---
> doc/guides/cryptodevs/qat.rst | 1 +
> doc/guides/rel_notes/release_17_11.rst | 6 ++++++
> drivers/crypto/qat/qat_crypto.c | 12 +++++-------
> drivers/crypto/qat/qat_crypto.h | 2 +-
> drivers/crypto/qat/qat_qp.c | 4 ++--
> 5 files changed, 15 insertions(+), 10 deletions(-)
>
...
> diff --git a/doc/guides/rel_notes/release_17_11.rst
> b/doc/guides/rel_notes/release_17_11.rst
> index 170f4f9..67b6f68 100644
> --- a/doc/guides/rel_notes/release_17_11.rst
> +++ b/doc/guides/rel_notes/release_17_11.rst
> @@ -41,6 +41,12 @@ New Features
> Also, make sure to start the actual text at the margin.
>
> =========================================================
>
> +* **Updated qat crypto PMD.**
"qat" should be in capital letters.
> +
> + Performance enhancements:
> +
> + * Removed atomics from the internal queue pair structure.
> +
>
next prev parent reply other threads:[~2017-09-04 14:39 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 ` Anatoly Burakov
2017-09-04 14:39 ` De Lara Guarch, Pablo [this message]
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 ` [dpdk-dev] [PATCH v2 0/3] performance enhancements for QAT driver De Lara Guarch, Pablo
2017-08-25 9:30 ` [dpdk-dev] [DPDK] [PATCH 2/3] qat: enable RX head writes coalescing 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=E115CCD9D858EF4F90C690B0DCB4D8976CC154EB@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).