DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
To: "Trahe, Fiona" <fiona.trahe@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
	"Jozwiak, TomaszX" <tomaszx.jozwiak@intel.com>
Subject: Re: [dpdk-dev] [PATCH v4] compress/qat: enable dynamic huffman encoding
Date: Wed, 17 Oct 2018 10:29:50 +0000	[thread overview]
Message-ID: <06EE24DD0B19E248B53F6DC8657831559EA31E@HASMSX110.ger.corp.intel.com> (raw)
In-Reply-To: <1539645382-17112-1-git-send-email-fiona.trahe@intel.com>



> -----Original Message-----
> From: Trahe, Fiona
> Sent: Tuesday, October 16, 2018 1:16 AM
> To: dev@dpdk.org
> Cc: akhil.goyal@nxp.com; Jozwiak, TomaszX <tomaszx.jozwiak@intel.com>;
> Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>; Trahe, Fiona
> <fiona.trahe@intel.com>
> Subject: [PATCH v4] compress/qat: enable dynamic huffman encoding
> 
> Enable dynamic huffman encoding in the QAT comp PMD.
> 
> Signed-off-by: Tomasz Jozwiak <tomaszx.jozwiak@intel.com>
> Signed-off-by: Fiona Trahe <fiona.trahe@intel.com>
> ---
> v4 changes:
>  - use #define for IM buffer logs, disable all by default
>    and use param for clearer hexdump length.
> 
> v3 changes:
>  - reverted to 1 buffer per intermediate buffer sgl
> 
> v2 changes:
>  - allocate 2 buffers per intermediate buffer sgl
>  - Compile out trace for debugging intermediate buffers
> 
>  config/common_base                       |   1 +
>  config/rte_config.h                      |   1 +
>  doc/guides/compressdevs/features/qat.ini |   1 +
>  doc/guides/compressdevs/qat_comp.rst     |   7 +-
>  drivers/common/qat/qat_device.c          |   4 +
>  drivers/common/qat/qat_device.h          |   7 ++
>  drivers/compress/qat/qat_comp.c          |  39 +++++++---
>  drivers/compress/qat/qat_comp.h          |  13 ++++
>  drivers/compress/qat/qat_comp_pmd.c      | 125
> ++++++++++++++++++++++++++++++-
>  9 files changed, 181 insertions(+), 17 deletions(-)
> 
> diff --git a/config/common_base b/config/common_base index
> 5519d71..29c71b1 100644
> --- a/config/common_base
> +++ b/config/common_base
> 2.7.4
Acked-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>

  reply	other threads:[~2018-10-17 10:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-20 17:46 [dpdk-dev] [PATCH] " Fiona Trahe
2018-10-05 16:18 ` [dpdk-dev] [PATCH v2] " Fiona Trahe
2018-10-09 11:01   ` Akhil Goyal
2018-10-09 14:09     ` Trahe, Fiona
2018-10-12 11:39       ` Akhil Goyal
2018-10-11 17:03   ` [dpdk-dev] [PATCH v3] " Fiona Trahe
2018-10-15 23:16     ` [dpdk-dev] [PATCH v4] " Fiona Trahe
2018-10-17 10:29       ` Kusztal, ArkadiuszX [this message]
2018-10-17 20:48       ` [dpdk-dev] [PATCH v5] " Fiona Trahe
2018-10-24 14:15         ` Akhil Goyal
2018-10-24 21:30           ` Thomas Monjalon
2018-10-25  0:40             ` Trahe, Fiona
2018-10-25  6:45               ` Thomas Monjalon
2018-10-25  1:30         ` [dpdk-dev] [PATCH v6] " Fiona Trahe
2018-10-25  7:34           ` Akhil Goyal
2018-10-26 18:18           ` [dpdk-dev] [PATCH v7] " Fiona Trahe
2018-10-27  0:06             ` Thomas Monjalon

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=06EE24DD0B19E248B53F6DC8657831559EA31E@HASMSX110.ger.corp.intel.com \
    --to=arkadiuszx.kusztal@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=tomaszx.jozwiak@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).