From: "Power, Ciara" <ciara.power@intel.com>
To: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "gakhil@marvell.com" <gakhil@marvell.com>, "Ji, Kai" <kai.ji@intel.com>
Subject: RE: [PATCH 2/3] common/qat: move command line params to the device struct
Date: Mon, 18 Sep 2023 16:01:59 +0000 [thread overview]
Message-ID: <SN7PR11MB7639494BD26BF3FF82BA5BB1E6FBA@SN7PR11MB7639.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230917154258.3509805-2-arkadiuszx.kusztal@intel.com>
Hi Arek,
> -----Original Message-----
> From: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>
> Sent: Sunday, September 17, 2023 4:43 PM
> To: dev@dpdk.org
> Cc: gakhil@marvell.com; Ji, Kai <kai.ji@intel.com>; Power, Ciara
> <ciara.power@intel.com>; Kusztal, ArkadiuszX
> <arkadiuszx.kusztal@intel.com>
> Subject: [PATCH 2/3] common/qat: move command line params to the device
> struct
>
> Command line parameters was moved to the device struct.
>
> Signed-off-by: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
> ---
> drivers/common/qat/qat_device.c | 54 ++++++++++++++++++--------------
> -----
> drivers/common/qat/qat_device.h | 35 ++++++++++++------------
> drivers/compress/qat/qat_comp_pmd.c | 9 +++----
> drivers/compress/qat/qat_comp_pmd.h | 3 +--
> drivers/crypto/qat/qat_asym.c | 13 +++++----
> drivers/crypto/qat/qat_sym.c | 23 ++++++++--------
> 6 files changed, 66 insertions(+), 71 deletions(-)
>
> diff --git a/drivers/common/qat/qat_device.c
> b/drivers/common/qat/qat_device.c index 93aef9aeb1..d9604e666d
> 100644
> --- a/drivers/common/qat/qat_device.c
> +++ b/drivers/common/qat/qat_device.c
> @@ -22,6 +22,16 @@
<snip>
> diff --git a/drivers/common/qat/qat_device.h
> b/drivers/common/qat/qat_device.h index 23d7f54b61..dcb5a42c89
> 100644
> --- a/drivers/common/qat/qat_device.h
> +++ b/drivers/common/qat/qat_device.h
> @@ -17,14 +17,21 @@
>
> #define QAT_DEV_NAME_MAX_LEN 64
>
> -#define QAT_LEGACY_CAPA "qat_legacy_capa"
> +#define QAT_LEGACY_CAPA_NAME "qat_legacy_capa"
> #define SYM_ENQ_THRESHOLD_NAME "qat_sym_enq_threshold"
> #define ASYM_ENQ_THRESHOLD_NAME "qat_asym_enq_threshold"
> #define COMP_ENQ_THRESHOLD_NAME "qat_comp_enq_threshold"
> #define SYM_CIPHER_CRC_ENABLE_NAME "qat_sym_cipher_crc_enable"
> -#define QAT_CMD_SLICE_MAP "qat_cmd_slice_disable"
> -#define QAT_CMD_SLICE_MAP_POS 5
> -#define MAX_QP_THRESHOLD_SIZE 32
> +#define QAT_CMD_SLICE_MAP_NAME "qat_cmd_slice_disable"
> +#define QAT_LEGACY_CAPA_POS 0
> +#define SYM_ENQ_THRESHOLD_POS 1
> +#define ASYM_ENQ_THRESHOLD_POS 2
> +#define COMP_ENQ_THRESHOLD_POS 3
> +#define SYM_CIPHER_CRC_ENABLE_POS 4
> +#define QAT_CMD_SLICE_MAP_POS 5
Small suggestion, maybe an enum could be used to group the above position macros together.
Acked-by: Ciara Power <ciara.power@intel.com>
next prev parent reply other threads:[~2023-09-18 16:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-17 15:42 [PATCH 1/3] common/qat: limit configuration to the primary process Arkadiusz Kusztal
2023-09-17 15:42 ` [PATCH 2/3] common/qat: move command line params to the device struct Arkadiusz Kusztal
2023-09-18 16:01 ` Power, Ciara [this message]
2023-09-17 15:42 ` [PATCH 3/3] common/qat: decouple pmds from the common code Arkadiusz Kusztal
2023-10-06 12:50 ` Power, Ciara
2023-10-06 13:02 ` Power, Ciara
2024-02-23 7:48 ` [PATCH v2 1/2] drivers/qat: isolate parser arguments configuration Arkadiusz Kusztal
2024-02-23 7:48 ` [PATCH v2 2/2] common/qat: decouple pmds from the common code Arkadiusz Kusztal
2024-02-29 9:30 ` [PATCH v3 1/3] common/qat: isolate parser arguments configuration Arkadiusz Kusztal
2024-02-29 9:30 ` [PATCH v3 2/3] common/qat: decouple pmds from the common code Arkadiusz Kusztal
2024-02-29 9:30 ` [PATCH v3 3/3] common/qat: fix incorrectly placed legacy flag Arkadiusz Kusztal
2023-09-18 15:07 ` [PATCH 1/3] common/qat: limit configuration to the primary process Power, Ciara
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=SN7PR11MB7639494BD26BF3FF82BA5BB1E6FBA@SN7PR11MB7639.namprd11.prod.outlook.com \
--to=ciara.power@intel.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=kai.ji@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).