DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Arek Kusztal <arkadiuszx.kusztal@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "fiona.trahe@intel.com" <fiona.trahe@intel.com>,
	"declan.doherty@intel.com" <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [PATCH v5 0/4] Add dual threading in QAT PMD
Date: Wed, 15 Jan 2020 15:48:39 +0000	[thread overview]
Message-ID: <VE1PR04MB6639AD21FB5167A768708B55E6370@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20200115143211.6176-1-arkadiuszx.kusztal@intel.com>

> 
> Remove the limitation whereby enqueue and dequeue must be
> done in same thread.
> The inflight calculation is reworked to be thread-safe for 2
> threads - note this is not general multi-thread support, i.e
> all enqueues to a qp must still be done in one thread and
> all dequeues must be done in one thread, but enqueues and
> dequeues may be in separate threads.
> As the tail-coalescing feature is not
> threadsafe it is removed first.
> Additional option added is to set minumum enqueue burst
> threshold which may help to reduce MMIO write occurances.
> 
> v5:
> - sent all patches in one patchset
> v4:
> - fixed checkpatch issues in 4th patch
> v3:
> - added minimum threshold option
> v2:
> - clarified wording in docs
> 
> Arek Kusztal (1):
>   crypto/qat: add minimum enq threshold to qat pmd
> 
> Fiona Trahe (3):
>   common/qat: remove tail write coalescing feature
>   common/qat: move max inflights param into qp
>   common/qat: add dual thread support
> 
>  doc/guides/compressdevs/qat_comp.rst |  5 +-
>  doc/guides/cryptodevs/qat.rst        | 28 +++++++++-
>  drivers/common/qat/qat_common.c      |  3 ++
>  drivers/common/qat/qat_common.h      |  3 ++
>  drivers/common/qat/qat_device.c      | 99
> +++++++++++++++++++++++++++++++-----
>  drivers/common/qat/qat_device.h      | 22 ++++++--
>  drivers/common/qat/qat_qp.c          | 86 +++++++++++++++++--------------
>  drivers/common/qat/qat_qp.h          | 14 +++--
>  drivers/compress/qat/qat_comp_pmd.c  | 14 ++++-
>  drivers/compress/qat/qat_comp_pmd.h  |  4 +-
>  drivers/crypto/qat/qat_asym_pmd.c    | 14 ++++-
>  drivers/crypto/qat/qat_asym_pmd.h    |  4 +-
>  drivers/crypto/qat/qat_sym_pmd.c     | 14 ++++-
>  drivers/crypto/qat/qat_sym_pmd.h     |  4 +-
>  14 files changed, 243 insertions(+), 71 deletions(-)
> 

Series Applied to dpdk-next-crypto

Thanks

      parent reply	other threads:[~2020-01-15 15:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15 14:32 Arek Kusztal
2020-01-15 14:32 ` [dpdk-dev] [PATCH v5 1/4] common/qat: remove tail write coalescing feature Arek Kusztal
2020-01-15 14:32 ` [dpdk-dev] [PATCH v5 2/4] common/qat: move max inflights param into qp Arek Kusztal
2020-01-15 14:32 ` [dpdk-dev] [PATCH v5 3/4] common/qat: add dual thread support Arek Kusztal
2020-01-15 14:32 ` [dpdk-dev] [PATCH v5 4/4] crypto/qat: add minimum enq threshold to qat pmd Arek Kusztal
2020-01-15 15:48 ` Akhil Goyal [this message]

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=VE1PR04MB6639AD21FB5167A768708B55E6370@VE1PR04MB6639.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@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).