From: Honnappa Nagarahalli <Honnappa.Nagarahalli@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>,
"igor.romanov@oktetlabs.ru" <igor.romanov@oktetlabs.ru>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
nd <nd@arm.com>, "aconole@redhat.com" <aconole@redhat.com>,
"l.wojciechow@partner.samsung.com"
<l.wojciechow@partner.samsung.com>, Phil Yang <Phil.Yang@arm.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH v3 2/2] test/service: fix race condition on stopping lcore
Date: Wed, 22 Jul 2020 21:40:37 +0000 [thread overview]
Message-ID: <DB6PR0802MB2216141E36D01AE4936D02E298790@DB6PR0802MB2216.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20200722103701.7244-2-harry.van.haaren@intel.com>
<snip>
> Subject: [PATCH v3 2/2] test/service: fix race condition on stopping lcore
>
> This commit fixes a potential race condition in the tests where the lcore
> running a service would increment a counter that was already reset by the
> test-suite thread. The resulting race-condition incremented value could cause
> CI failures, as indicated by DPDK's CI.
>
> This patch fixes the race-condition by making use of the added
> rte_service_lcore_active() API, which indicates when a service-core is no
> longer in the service-core polling loop.
>
> The unit test makes use of the above function to detect when all statistics
> increments are done in the service-core thread, and then the unit test
> continues finalizing and checking state.
>
> Fixes: f28f3594ded2 ("service: add attribute API")
>
> Reported-by: David Marchand <david.marchand@redhat.com>
> Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com>
> Reviewed-by: Phil Yang <phil.yang@arm.com>
Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
>
> ---
>
> v3:
> - Refactor while() to for() to simplify (Harry)
> - Use SERVICE_DELAY instead of magic const 1 (Phil)
> - Add Phil's reviewed by tag from ML
>
> v2:
> Thanks for discussion on v1, this v2 fixup for the CI including previous
> feedback on ML.
> ---
> app/test/test_service_cores.c | 20 +++++++++++++++++++-
> 1 file changed, 19 insertions(+), 1 deletion(-)
>
> diff --git a/app/test/test_service_cores.c b/app/test/test_service_cores.c index
> ef1d8fcb9..a6bc4487e 100644
> --- a/app/test/test_service_cores.c
> +++ b/app/test/test_service_cores.c
> @@ -362,6 +362,9 @@ service_lcore_attr_get(void)
> "Service core add did not return zero");
> TEST_ASSERT_EQUAL(0, rte_service_map_lcore_set(id, slcore_id, 1),
> "Enabling valid service and core failed");
> + /* Ensure service is not active before starting */
> + TEST_ASSERT_EQUAL(0, rte_service_lcore_active(slcore_id),
> + "Not-active service core reported as active");
> TEST_ASSERT_EQUAL(0, rte_service_lcore_start(slcore_id),
> "Starting service core failed");
>
> @@ -382,7 +385,22 @@ service_lcore_attr_get(void)
> lcore_attr_id, &lcore_attr_value),
> "Invalid lcore attr didn't return -EINVAL");
>
> - rte_service_lcore_stop(slcore_id);
> + /* Ensure service is active */
> + TEST_ASSERT_EQUAL(1, rte_service_lcore_active(slcore_id),
> + "Active service core reported as not-active");
> +
> + TEST_ASSERT_EQUAL(0, rte_service_map_lcore_set(id, slcore_id, 0),
> + "Disabling valid service and core failed");
> + TEST_ASSERT_EQUAL(0, rte_service_lcore_stop(slcore_id),
> + "Failed to stop service lcore");
> +
> + /* Wait until service lcore not active, or for 100x SERVICE_DELAY */
> + for (int i = 0; i < 100 && rte_service_lcore_active(slcore_id) == 1;
> + i++)
> + rte_delay_ms(SERVICE_DELAY);
> +
> + TEST_ASSERT_EQUAL(0, rte_service_lcore_active(slcore_id),
> + "Service lcore not stopped after waiting.");
>
> TEST_ASSERT_EQUAL(0, rte_service_lcore_attr_reset_all(slcore_id),
> "Valid lcore_attr_reset_all() didn't return success");
> --
> 2.17.1
next prev parent reply other threads:[~2020-07-22 21:40 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200720120850eucas1p10debcafa273d244a7e63d225c50cc9df@eucas1p1.samsung.com>
2020-07-20 12:09 ` [dpdk-dev] [PATCH] service: fix stop API to wait for service thread Harry van Haaren
2020-07-20 12:51 ` Lukasz Wojciechowski
2020-07-20 14:20 ` Van Haaren, Harry
2020-07-20 14:38 ` [dpdk-dev] [PATCH v2 1/2] service: add API to retrieve service core active Harry van Haaren
2020-07-20 14:38 ` [dpdk-dev] [PATCH v2 2/2] test/service: fix race condition on stopping lcore Harry van Haaren
2020-07-20 17:45 ` Lukasz Wojciechowski
2020-07-21 8:38 ` Phil Yang
2020-07-22 10:26 ` Van Haaren, Harry
2020-07-20 17:45 ` [dpdk-dev] [PATCH v2 1/2] service: add API to retrieve service core active Lukasz Wojciechowski
2020-07-21 7:47 ` Phil Yang
2020-07-21 19:43 ` Honnappa Nagarahalli
2020-07-21 19:50 ` David Marchand
2020-07-21 20:23 ` Honnappa Nagarahalli
2020-07-22 10:14 ` Van Haaren, Harry
2020-07-22 18:50 ` Honnappa Nagarahalli
2020-07-23 16:59 ` Van Haaren, Harry
2020-07-22 10:37 ` [dpdk-dev] [PATCH v3 " Harry van Haaren
2020-07-22 10:37 ` [dpdk-dev] [PATCH v3 2/2] test/service: fix race condition on stopping lcore Harry van Haaren
2020-07-22 21:40 ` Honnappa Nagarahalli [this message]
2020-07-22 21:39 ` [dpdk-dev] [PATCH v3 1/2] service: add API to retrieve service core active Honnappa Nagarahalli
2020-07-24 12:45 ` [dpdk-dev] [PATCH v4 " Harry van Haaren
2020-07-24 12:45 ` [dpdk-dev] [PATCH v4 2/2] test/service: fix race condition on stopping lcore Harry van Haaren
2020-07-24 13:45 ` [dpdk-dev] [PATCH v5 1/2] service: add API to retrieve service core active Harry van Haaren
2020-07-24 13:45 ` [dpdk-dev] [PATCH v5 2/2] test/service: fix race condition on stopping lcore Harry van Haaren
2020-09-14 8:36 ` David Marchand
2020-09-14 14:33 ` Van Haaren, Harry
2020-09-14 14:31 ` [dpdk-dev] [PATCH v6 1/2] service: add API to retrieve service core active Harry van Haaren
2020-09-14 14:31 ` [dpdk-dev] [PATCH v6 2/2] test/service: fix race condition on stopping lcore Harry van Haaren
2020-09-21 14:51 ` David Marchand
2020-10-13 19:45 ` David Marchand
2020-10-15 8:11 ` Van Haaren, Harry
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=DB6PR0802MB2216141E36D01AE4936D02E298790@DB6PR0802MB2216.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=Phil.Yang@arm.com \
--cc=aconole@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=harry.van.haaren@intel.com \
--cc=igor.romanov@oktetlabs.ru \
--cc=l.wojciechow@partner.samsung.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).