DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Adam Dybkowski <adamx.dybkowski@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	 "fiona.trahe@intel.com" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] drivers/qat: im buffer too small - split op
Date: Wed, 1 Apr 2020 14:20:22 +0000	[thread overview]
Message-ID: <DB8PR04MB66354EDCC60CE952B6EFAF23E6C90@DB8PR04MB6635.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20200318163349.1789-1-adamx.dybkowski@intel.com>

Hi Fiona,

Could you please review this patchset.
> 
> This patch implements a special way of buffer handling when internal
> QAT IM buffer is too small for Huffman dynamic compression operation.
> Instead of falling back to fixed compression, the operation is now
> split into multiple smaller dynamic compression requests (possible to
> execute on QAT) and their results are then combined and copied into
> the output buffer. This is not possible if any checksum calculation
> was requested - in such case the code falls back to fixed compression
> as before.
> 
> Signed-off-by: Adam Dybkowski <adamx.dybkowski@intel.com>
> ---
>  drivers/common/qat/qat_qp.c         | 231 ++++++++++++--
>  drivers/common/qat/qat_qp.h         |   7 +
>  drivers/compress/qat/qat_comp.c     | 458 +++++++++++++++++++++++++---
>  drivers/compress/qat/qat_comp.h     |  22 +-
>  drivers/compress/qat/qat_comp_pmd.c |  24 +-
>  5 files changed, 669 insertions(+), 73 deletions(-)
> 

      parent reply	other threads:[~2020-04-01 14:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18 16:33 Adam Dybkowski
2020-03-18 16:33 ` [dpdk-dev] [PATCH 2/2] test/compress: im buffer too small - add unit tests Adam Dybkowski
2020-04-01 14:20 ` Akhil Goyal [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=DB8PR04MB66354EDCC60CE952B6EFAF23E6C90@DB8PR04MB6635.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=adamx.dybkowski@intel.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@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).