From: Artur Trybula <arturx.trybula@intel.com>
To: dev@dpdk.org, fiona.trahe@intel.com, shallyv@marvell.com,
adamx.dybkowski@intel.com, arturx.trybula@intel.com,
akhil.goyal@nxp.com
Subject: [dpdk-dev] [PATCH 1/2] compress/qat: overflow catching
Date: Fri, 6 Sep 2019 13:11:37 +0200 [thread overview]
Message-ID: <20190906111138.1582-1-arturx.trybula@intel.com> (raw)
Out-of-space recoverable feature added to QuickAssist compressdev driver
Signed-off-by: Artur Trybula <arturx.trybula@intel.com>
---
drivers/compress/qat/qat_comp.c | 25 ++++++++++++++++++++++---
1 file changed, 22 insertions(+), 3 deletions(-)
diff --git a/drivers/compress/qat/qat_comp.c b/drivers/compress/qat/qat_comp.c
index 835aaa838..aa43df6b1 100644
--- a/drivers/compress/qat/qat_comp.c
+++ b/drivers/compress/qat/qat_comp.c
@@ -259,10 +259,29 @@ qat_comp_process_response(void **op, uint8_t *resp, void *op_cookie,
(!cmp_err_code && xlat_err_code == ERR_CODE_OVERFLOW_ERROR)
||
(cmp_err_code == ERR_CODE_OVERFLOW_ERROR &&
- xlat_err_code == ERR_CODE_OVERFLOW_ERROR))
- rx_op->status =
+ xlat_err_code == ERR_CODE_OVERFLOW_ERROR)) {
+
+ struct icp_qat_fw_resp_comp_pars *comp_resp =
+ (struct icp_qat_fw_resp_comp_pars *)&resp_msg->comp_resp_pars;
+
+ if (comp_resp->input_byte_counter) {
+ if ((qat_xform->qat_comp_request_type
+ == QAT_COMP_REQUEST_FIXED_COMP_STATELESS) ||
+ (qat_xform->qat_comp_request_type
+ == QAT_COMP_REQUEST_DYNAMIC_COMP_STATELESS)) {
+ rx_op->status =
+ RTE_COMP_OP_STATUS_OUT_OF_SPACE_RECOVERABLE;
+ rx_op->consumed =
+ comp_resp->input_byte_counter;
+ rx_op->produced =
+ comp_resp->output_byte_counter;
+ } else
+ rx_op->status =
RTE_COMP_OP_STATUS_OUT_OF_SPACE_TERMINATED;
- else
+ } else
+ rx_op->status =
+ RTE_COMP_OP_STATUS_OUT_OF_SPACE_TERMINATED;
+ } else
rx_op->status = RTE_COMP_OP_STATUS_ERROR;
++(*dequeue_err_count);
--
2.17.1
next reply other threads:[~2019-09-06 11:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 11:11 Artur Trybula [this message]
2019-09-06 11:11 ` [dpdk-dev] [PATCH 2/2] test/compress: unit test for stateless overflow recovery Artur Trybula
2019-09-26 9:32 ` [dpdk-dev] [PATCH v2 0/2] Add overflow recovery for stateless compression Artur Trybula
2019-09-26 9:32 ` [dpdk-dev] [PATCH v2 1/2] compress/qat: overflow catch " Artur Trybula
2019-09-26 9:32 ` [dpdk-dev] [PATCH v2 2/2] test/compress: unit test for stateless overflow recovery Artur Trybula
2019-10-11 17:46 ` [dpdk-dev] [PATCH v3 0/2] Add overflow recovery for stateless compression Artur Trybula
2019-10-11 17:46 ` [dpdk-dev] [PATCH v3 1/2] compress/qat: overflow catch " Artur Trybula
2019-10-14 13:38 ` Trahe, Fiona
2019-10-11 17:46 ` [dpdk-dev] [PATCH v3 2/2] test/compress: unit test for stateless overflow recovery Artur Trybula
2019-10-14 13:48 ` Trahe, Fiona
2019-10-14 14:20 ` Trybula, ArturX
2019-10-16 9:40 ` [dpdk-dev] [PATCH v4 0/2] Add overflow recovery for stateless compression Artur Trybula
2019-10-16 9:40 ` [dpdk-dev] [PATCH v4 1/2] compress/qat: overflow catch " Artur Trybula
2019-10-16 9:40 ` [dpdk-dev] [PATCH v4 2/2] test/compress: unit test for stateless overflow recovery Artur Trybula
2019-10-16 11:16 ` [dpdk-dev] [PATCH v4 0/2] Add overflow recovery for stateless compression Trahe, Fiona
2019-10-16 13:13 ` 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=20190906111138.1582-1-arturx.trybula@intel.com \
--to=arturx.trybula@intel.com \
--cc=adamx.dybkowski@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=shallyv@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).