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>
Subject: RE: [PATCH v3 1/2] common/qat: read hw slice configuration
Date: Thu, 20 Oct 2022 14:08:22 +0000 [thread overview]
Message-ID: <SN6PR11MB34084C24AC296A7F8F6DAF97812A9@SN6PR11MB3408.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221018140154.35221-1-arkadiuszx.kusztal@intel.com>
Acked-by: Kai Ji <kai.ji@intel.com>
> -----Original Message-----
> From: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>
> Sent: Tuesday, October 18, 2022 3:02 PM
> To: dev@dpdk.org
> Cc: gakhil@marvell.com; Ji, Kai <kai.ji@intel.com>; Kusztal, ArkadiuszX
> <arkadiuszx.kusztal@intel.com>
> Subject: [PATCH v3 1/2] common/qat: read hw slice configuration
>
> Read slice configuration of QAT capabilities.
> This will allow to recognize if specific hw function is available on particular
> device.
>
> Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> ---
> v2:
> - added generation specific functions
> v3:
> - split into two patches
> - fixed checkpatch issues
>
> drivers/common/qat/dev/qat_dev_gen1.c | 8 ++++++++
> drivers/common/qat/dev/qat_dev_gen2.c | 8 ++++++++
> drivers/common/qat/dev/qat_dev_gen3.c | 13 +++++++++++++
> drivers/common/qat/dev/qat_dev_gen4.c | 8 ++++++++
> drivers/common/qat/qat_adf/icp_qat_hw.h | 18 ++++++++++++++++++
> drivers/common/qat/qat_device.c | 10 +++++++++-
> drivers/common/qat/qat_device.h | 8 +++++++-
> 7 files changed, 71 insertions(+), 2 deletions(-)
>
next prev parent reply other threads:[~2022-10-20 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 14:01 Arek Kusztal
2022-10-18 14:01 ` [PATCH v3 2/2] crypto/qat: " Arek Kusztal
2022-10-20 14:09 ` Ji, Kai
2022-10-20 14:08 ` Ji, Kai [this message]
2022-10-21 13:39 ` [PATCH v3 1/2] common/qat: " Akhil Goyal
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=SN6PR11MB34084C24AC296A7F8F6DAF97812A9@SN6PR11MB3408.namprd11.prod.outlook.com \
--to=kai.ji@intel.com \
--cc=arkadiuszx.kusztal@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).