From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "Trybula, ArturX" <arturx.trybula@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"shallyv@marvell.com" <shallyv@marvell.com>,
"Dybkowski, AdamX" <adamx.dybkowski@intel.com>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Subject: Re: [dpdk-dev] [PATCH v4 0/2] Add overflow recovery for stateless compression
Date: Wed, 16 Oct 2019 11:16:15 +0000 [thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B435A2174C0C@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <20191016094045.19895-1-arturx.trybula@intel.com>
> -----Original Message-----
> From: Trybula, ArturX
> Sent: Wednesday, October 16, 2019 10:41 AM
> To: dev@dpdk.org; Trahe, Fiona <fiona.trahe@intel.com>; shallyv@marvell.com; Dybkowski, AdamX
> <adamx.dybkowski@intel.com>; Trybula, ArturX <arturx.trybula@intel.com>; akhil.goyal@nxp.com
> Subject: [PATCH v4 0/2] Add overflow recovery for stateless compression
>
> This patch adds out-of-space recoverable feature for stateless
> compression scenario to QuickAssist compressdev driver. Unit test
> was also created to verify the new feature.
>
> v4: - if a device doesn't support out-of-space recoverable feature,
> then instead of "failed", "unsupported" result will be
> printed out on the screen
>
> v3: - rebasing onto the recent master
>
> v2: - rebasing over the external mbufs
>
> Artur Trybula (2):
> compress/qat: overflow catch for stateless compression
> test/compress: unit test for stateless overflow recovery
>
> app/test/test_compressdev.c | 280 ++++++++++++++++++++++++++------
> drivers/compress/qat/qat_comp.c | 28 +++-
> 2 files changed, 258 insertions(+), 50 deletions(-)
>
> --
> 2.17.1
Series
Acked-by: Fiona Trahe <fiona.trahe@intel.com>
next prev parent reply other threads:[~2019-10-16 11:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 11:11 [dpdk-dev] [PATCH 1/2] compress/qat: overflow catching Artur Trybula
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 ` Trahe, Fiona [this message]
2019-10-16 13:13 ` [dpdk-dev] [PATCH v4 0/2] Add overflow recovery for stateless compression 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=348A99DA5F5B7549AA880327E580B435A2174C0C@IRSMSX101.ger.corp.intel.com \
--to=fiona.trahe@intel.com \
--cc=adamx.dybkowski@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=arturx.trybula@intel.com \
--cc=dev@dpdk.org \
--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).