DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ji, Kai" <kai.ji@intel.com>
To: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "gakhil@marvell.com" <gakhil@marvell.com>,
	"Power, Ciara" <ciara.power@intel.com>
Subject: Re: [PATCH v5] common/qat: add virtual qat device (vQAT)
Date: Fri, 1 Mar 2024 15:48:27 +0000	[thread overview]
Message-ID: <DS0PR11MB74583B8C4E0D3A875BCDD21E815E2@DS0PR11MB7458.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20240301151923.4906-1-arkadiuszx.kusztal@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1627 bytes --]

Acked-by: Kai Ji <kai.ji@intel.com>


________________________________
From: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Sent: 01 March 2024 15:19
To: dev@dpdk.org <dev@dpdk.org>
Cc: gakhil@marvell.com <gakhil@marvell.com>; Power, Ciara <ciara.power@intel.com>; Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>
Subject: [PATCH v5] common/qat: add virtual qat device (vQAT)

This commit adds virtual QAT device to the Intel
QuickAssist Technology PMD. There are three kinds of
virtual QAT device defined which offer different QAT
service to the customers: symmetric crypto, asymmetric
crypto and compression.

Signed-off-by: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
---
v2:
- added symmetric crypto qp config
v3:
- added compression
- added asymmetric crypto
v4:
- rebased to fix a release notes issue
v5:
- rebased against newest changes to the pmd

 doc/guides/rel_notes/release_24_03.rst       |  4 ++
 drivers/common/qat/dev/qat_dev_gen4.c        | 55 +++++++++++++++++++++++++++-
 drivers/common/qat/qat_adf/icp_qat_hw.h      |  5 +++
 drivers/common/qat/qat_common.h              |  1 +
 drivers/common/qat/qat_device.c              |  7 +++-
 drivers/compress/qat/dev/qat_comp_pmd_gen4.c | 18 ++++++---
 drivers/compress/qat/qat_comp_pmd.c          |  7 ++++
 drivers/crypto/qat/dev/qat_crypto_pmd_gen4.c | 24 ++++++++----
 drivers/crypto/qat/qat_asym.c                |  7 ++++
 drivers/crypto/qat/qat_sym.c                 |  7 ++++
 drivers/crypto/qat/qat_sym_session.c         | 18 ++++++---
 11 files changed, 131 insertions(+), 22 deletions(-)

--
2.13.6


[-- Attachment #2: Type: text/html, Size: 3242 bytes --]

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

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-18 13:41 [PATCH 1/2] common/qat: add vqat definition to pmd map Arkadiusz Kusztal
2023-12-18 13:41 ` [PATCH 2/2] common/qat: add vqat confiuration macros Arkadiusz Kusztal
2024-02-18 22:25 ` [PATCH v2] common/qat: add symmetric crypto virtual qat device (vQAT) Arkadiusz Kusztal
2024-02-21  7:50   ` [PATCH v3] common/qat: add " Arkadiusz Kusztal
2024-02-22 12:20     ` Power, Ciara
2024-02-29 10:21     ` [PATCH v4] " Arkadiusz Kusztal
2024-02-29 10:27       ` Power, Ciara
2024-03-01  6:15       ` [EXTERNAL] " Akhil Goyal
2024-03-01 15:19       ` [PATCH v5] " Arkadiusz Kusztal
2024-03-01 15:24         ` [EXTERNAL] " Akhil Goyal
2024-03-04  7:07           ` Akhil Goyal
2024-03-01 15:48         ` Ji, Kai [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=DS0PR11MB74583B8C4E0D3A875BCDD21E815E2@DS0PR11MB7458.namprd11.prod.outlook.com \
    --to=kai.ji@intel.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=ciara.power@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.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).