From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Ciara Power <ciara.power@intel.com>
Cc: stable@dpdk.org, roy.fan.zhang@intel.com,
Anoob Joseph <anoobj@marvell.com>,
Declan Doherty <declan.doherty@intel.com>
Subject: Re: [PATCH 19.11] test/crypto: fix unnecessary stats retrieval
Date: Wed, 1 Dec 2021 16:38:38 +0100 [thread overview]
Message-ID: <CAATJJ0KRJ=YwPim4cgbDn66QO2BOPSfsaLydtQYw05x9AKRo3g@mail.gmail.com> (raw)
In-Reply-To: <20211201110312.2263792-1-ciara.power@intel.com>
On Wed, Dec 1, 2021 at 12:03 PM Ciara Power <ciara.power@intel.com> wrote:
>
> [ upstream commit c0daf3bd4b4e36375f8c338092975d61ec03a98f ]
>
Thanks, applied
> The device stats are retrieved in the testcase teardown function,
> but are not being used afterwards. Remove this unnecessary call.
>
> Fixes: 202d375c60bc ("app/test: add cryptodev unit and performance tests")
>
> Signed-off-by: Ciara Power <ciara.power@intel.com>
> Acked-by: Anoob Joseph <anoobj@marvell.com>
> ---
> app/test/test_cryptodev.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/app/test/test_cryptodev.c b/app/test/test_cryptodev.c
> index 189f7be4a..c1fee1686 100644
> --- a/app/test/test_cryptodev.c
> +++ b/app/test/test_cryptodev.c
> @@ -581,7 +581,6 @@ ut_teardown(void)
> {
> struct crypto_testsuite_params *ts_params = &testsuite_params;
> struct crypto_unittest_params *ut_params = &unittest_params;
> - struct rte_cryptodev_stats stats;
>
> /* free crypto session structure */
> #ifdef RTE_LIBRTE_SECURITY
> @@ -628,8 +627,6 @@ ut_teardown(void)
> RTE_LOG(DEBUG, USER1, "CRYPTO_MBUFPOOL count %u\n",
> rte_mempool_avail_count(ts_params->mbuf_pool));
>
> - rte_cryptodev_stats_get(ts_params->valid_devs[0], &stats);
> -
> /* Stop the device */
> rte_cryptodev_stop(ts_params->valid_devs[0]);
> }
> --
> 2.25.1
>
--
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd
prev parent reply other threads:[~2021-12-01 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 11:03 Ciara Power
2021-12-01 15:38 ` Christian Ehrhardt [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='CAATJJ0KRJ=YwPim4cgbDn66QO2BOPSfsaLydtQYw05x9AKRo3g@mail.gmail.com' \
--to=christian.ehrhardt@canonical.com \
--cc=anoobj@marvell.com \
--cc=ciara.power@intel.com \
--cc=declan.doherty@intel.com \
--cc=roy.fan.zhang@intel.com \
--cc=stable@dpdk.org \
/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).