From: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/4] Refactor of debug information on cryptodev tests
Date: Wed, 15 Jun 2016 14:42:53 +0000 [thread overview]
Message-ID: <9F7182E3F746AB4EA17801C148F3C60409D97E75@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <1465999880-24438-1-git-send-email-pablo.de.lara.guarch@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Pablo de Lara
> Sent: Wednesday, June 15, 2016 3:11 PM
> To: dev@dpdk.org
> Cc: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> Subject: [dpdk-dev] [PATCH v2 0/4] Refactor of debug information on
> cryptodev tests
>
> The cryptodev unit tests were using the macro RTE_APP_TEST_DEBUG,
> which is not used in any other tests, to dump memory for debugging
> purposes.
> Instead, a new macro TEST_HEXDUMP will be used to dump memory (calling
> rte_hexdump), when RTE_LOG_LEVEL is set to RTE_LOG_DEBUG.
>
> This patchset depends on the patchset "rework crypto AES unit test":
> http://dpdk.org/ml/archives/dev/2016-June/041572.html
>
> Changes in v2:
> - Use new TEST_HEXDUMP macro in new test_cryptodev_aes.c file.
>
> Pablo de Lara (4):
> test: remove useless hexdump include
> test: fix compilation when RTE_APP_TEST_DEBUG was set
> test: remove unnecessary hexdump_mbuf_data and HEXDUMP
> app: add new TEST_HEXDUMP macro
>
> app/test/test.h | 7 ++
> app/test/test_cryptodev.c | 165 ++++++++++++++---------------------------
> app/test/test_cryptodev_aes.c | 6 +-
> app/test/test_cryptodev_perf.c | 1 -
> 4 files changed, 65 insertions(+), 114 deletions(-)
>
> --
> 2.5.0
Series-acked-by: Fan Zhang <roy.fan.zhang@intel.com>
next prev parent reply other threads:[~2016-06-15 14:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 13:01 [dpdk-dev] [PATCH " Pablo de Lara
2016-06-15 13:01 ` [dpdk-dev] [PATCH 1/4] test: remove useless hexdump include Pablo de Lara
2016-06-15 13:01 ` [dpdk-dev] [PATCH 2/4] test: fix compilation when RTE_APP_TEST_DEBUG was set Pablo de Lara
2016-06-15 13:01 ` [dpdk-dev] [PATCH 3/4] test: remove unnecessary hexdump_mbuf_data and HEXDUMP Pablo de Lara
2016-06-15 13:01 ` [dpdk-dev] [PATCH 4/4] app: add new TEST_HEXDUMP macro Pablo de Lara
2016-06-15 14:03 ` [dpdk-dev] [PATCH 0/4] Refactor of debug information on cryptodev tests De Lara Guarch, Pablo
2016-06-15 14:11 ` [dpdk-dev] [PATCH v2 " Pablo de Lara
2016-06-15 14:11 ` [dpdk-dev] [PATCH v2 1/4] test: remove useless hexdump include Pablo de Lara
2016-06-15 14:11 ` [dpdk-dev] [PATCH v2 2/4] test: fix compilation when RTE_APP_TEST_DEBUG was set Pablo de Lara
2016-06-15 14:11 ` [dpdk-dev] [PATCH v2 3/4] test: remove unnecessary hexdump_mbuf_data and HEXDUMP Pablo de Lara
2016-06-15 14:11 ` [dpdk-dev] [PATCH v2 4/4] app: add new TEST_HEXDUMP macro Pablo de Lara
2016-06-15 14:42 ` Zhang, Roy Fan [this message]
2016-06-20 15:48 ` [dpdk-dev] [PATCH v2 0/4] Refactor of debug information on cryptodev tests 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=9F7182E3F746AB4EA17801C148F3C60409D97E75@IRSMSX101.ger.corp.intel.com \
--to=roy.fan.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@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).