From: Phil Yang <Phil.Yang@arm.com>
To: Harry van Haaren <harry.van.haaren@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "david.marchand@redhat.com" <david.marchand@redhat.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH v2] test/service: add perf test for service on app lcore
Date: Thu, 7 May 2020 06:28:48 +0000 [thread overview]
Message-ID: <VE1PR08MB4640B811797B8843CE6B26E9E9A50@VE1PR08MB4640.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20200506171642.32105-1-harry.van.haaren@intel.com>
> -----Original Message-----
> From: Harry van Haaren <harry.van.haaren@intel.com>
> Sent: Thursday, May 7, 2020 1:17 AM
> To: dev@dpdk.org
> Cc: david.marchand@redhat.com; Phil Yang <Phil.Yang@arm.com>;
> Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>; Harry van Haaren
> <harry.van.haaren@intel.com>
> Subject: [PATCH v2] test/service: add perf test for service on app lcore
>
> This commit adds a basic test to check the cycle cost
> of related to calling into a service.
>
> Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com>
>
> ---
>
> v2:
> - Add space at start of output (Phil Yang)
> - Fix compile error on older GCCs (David Marchand)
>
> ---
> app/test/test_service_cores.c | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/app/test/test_service_cores.c b/app/test/test_service_cores.c
> index a922c7ddc..75a3f8b45 100644
> --- a/app/test/test_service_cores.c
> +++ b/app/test/test_service_cores.c
> @@ -789,8 +789,19 @@ service_app_lcore_poll_impl(const int mt_safe)
> "MT Unsafe: App core1 didn't return -
> EBUSY");
> }
>
> - unregister_all();
> + /* Performance test: call in a loop, and measure tsc() */
> + uint32_t i;
> + const uint32_t perf_iters = (1 << 12);
> + uint64_t start = rte_rdtsc();
> + for (i = 0; i < perf_iters; i++) {
> + int err = service_run_on_app_core_func(&id);
> + TEST_ASSERT_EQUAL(0, err, "perf test: returned run failure");
> + }
> + uint64_t end = rte_rdtsc();
> + printf("\t\tperf test for %s: %0.1f cycles per call\n", mt_safe ?
This print will be printed before the function test result.
Apologize for my previous comments. Please ignore it.
A nitpick comment on formatting the output.
- printf("\t\tperf test for %s: %0.1f cycles per call\n", mt_safe ?
+ printf("Perf test for %-10s: %0.1f cycles per call\n", mt_safe ?
Tested-by: Phil Yang <phil.yang@arm.com>
Reviewed-by: Phil Yang <phil.yang@arm.com>
Thanks,
Phil
> + "MT Safe" : "MT Unsafe", (end - start)/(float)perf_iters);
>
> + unregister_all();
> return TEST_SUCCESS;
> }
>
> --
> 2.17.1
next prev parent reply other threads:[~2020-05-07 6:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200501155607eucas1p2509870b6b5f4cc520dca11888e221b1b@eucas1p2.samsung.com>
2020-05-01 15:56 ` [dpdk-dev] [PATCH] " Harry van Haaren
2020-05-04 20:50 ` Lukasz Wojciechowski
2020-05-05 10:21 ` Van Haaren, Harry
2020-05-05 12:38 ` Lukasz Wojciechowski
2020-05-06 14:33 ` Phil Yang
2020-05-06 15:44 ` David Marchand
2020-05-06 17:00 ` Van Haaren, Harry
2020-05-06 17:16 ` [dpdk-dev] [PATCH v2] " Harry van Haaren
2020-05-07 6:28 ` Phil Yang [this message]
2020-05-07 12:11 ` David Marchand
2020-05-11 11:20 ` David Marchand
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=VE1PR08MB4640B811797B8843CE6B26E9E9A50@VE1PR08MB4640.eurprd08.prod.outlook.com \
--to=phil.yang@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=nd@arm.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).