DPDK patches and discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Jozwiak, TomaszX" <tomaszx.jozwiak@intel.com>,
	"Trahe, Fiona" <fiona.trahe@intel.com>,
	"Jozwiak, TomaszX" <tomaszx.jozwiak@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 0/5] crypto/qat: move to dynamic logging
Date: Thu, 14 Jun 2018 14:05:26 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8977F8D4533@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1528974186-13370-1-git-send-email-tomaszx.jozwiak@intel.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Tomasz Jozwiak
> Sent: Thursday, June 14, 2018 12:03 PM
> To: Trahe, Fiona <fiona.trahe@intel.com>; Jozwiak, TomaszX
> <tomaszx.jozwiak@intel.com>; dev@dpdk.org
> Subject: [dpdk-dev] [PATCH v2 0/5] crypto/qat: move to dynamic logging
> 
> Note this patchset is targeting 18.08 release and depends on the qat refactoring
> patchset:
> http://dpdk.org/ml/archives/dev/2018-May/101306.html
> 
> Move to dynamic logging and cleanup trace.
> 
> Changes for v2:
>  - fixed some bugs detected in patch 2/5 when using clang
> 
> Fiona Trahe (2):
>   crypto/qat: rename log macro for non-dp logs
>   doc/qat: document debug options
> 
> Tomasz Jozwiak (3):
>   crypto/qat: cleanup unused and useless trace
>   crypto/qat: move to dynamic logging for non-dp trace
>   crypto/qat: move to dynamic logging for data-path trace
> 
>  config/common_base                   |   4 --
>  doc/guides/cryptodevs/qat.rst        |  26 +++++++++
>  drivers/crypto/qat/Makefile          |   1 +
>  drivers/crypto/qat/meson.build       |   1 +
>  drivers/crypto/qat/qat_common.c      |  12 ++--
>  drivers/crypto/qat/qat_device.c      |  12 ++--
>  drivers/crypto/qat/qat_logs.c        |  40 ++++++++++++++
>  drivers/crypto/qat/qat_logs.h        |  65 +++++++++-------------
>  drivers/crypto/qat/qat_qp.c          |  63 +++++++++------------
>  drivers/crypto/qat/qat_sym.c         |  65 +++++++++++-----------
>  drivers/crypto/qat/qat_sym.h         |  30 +++++-----
>  drivers/crypto/qat/qat_sym_pmd.c     |  21 +++----
>  drivers/crypto/qat/qat_sym_session.c | 103 ++++++++++++++++-------------------
>  13 files changed, 234 insertions(+), 209 deletions(-)  create mode 100644
> drivers/crypto/qat/qat_logs.c
> 
> --
> 2.7.4

Applied to dpdk-next-crypto.
Thanks,

Pablo

      parent reply	other threads:[~2018-06-14 14:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-11 11:31 [dpdk-dev] [PATCH " Fiona Trahe
2018-05-11 11:31 ` [dpdk-dev] [PATCH 1/5] crypto/qat: cleanup unused and useless trace Fiona Trahe
2018-05-11 11:31 ` [dpdk-dev] [PATCH 2/5] crypto/qat: move to dynamic logging for non-dp trace Fiona Trahe
2018-06-12 15:54   ` De Lara Guarch, Pablo
2018-05-11 11:31 ` [dpdk-dev] [PATCH 3/5] crypto/qat: rename log macro for non-dp logs Fiona Trahe
2018-05-11 11:31 ` [dpdk-dev] [PATCH 4/5] crypto/qat: move to dynamic logging for data-path trace Fiona Trahe
2018-05-11 11:31 ` [dpdk-dev] [PATCH 5/5] doc/qat: document debug options Fiona Trahe
2018-06-14 11:03 ` [dpdk-dev] [PATCH v2 0/5] crypto/qat: move to dynamic logging Tomasz Jozwiak
2018-06-14 11:03   ` [dpdk-dev] [PATCH v2 1/5] crypto/qat: cleanup unused and useless trace Tomasz Jozwiak
2018-06-14 11:03   ` [dpdk-dev] [PATCH v2 2/5] crypto/qat: move to dynamic logging for non-dp trace Tomasz Jozwiak
2018-06-14 11:03   ` [dpdk-dev] [PATCH v2 3/5] crypto/qat: rename log macro for non-dp logs Tomasz Jozwiak
2018-06-14 11:03   ` [dpdk-dev] [PATCH v2 4/5] crypto/qat: move to dynamic logging for data-path trace Tomasz Jozwiak
2018-06-14 11:03   ` [dpdk-dev] [PATCH v2 5/5] doc/qat: document debug options Tomasz Jozwiak
2018-06-14 14:05   ` De Lara Guarch, Pablo [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=E115CCD9D858EF4F90C690B0DCB4D8977F8D4533@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.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).