From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "Van Haaren, Harry" <harry.van.haaren@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Phil Yang <Phil.Yang@arm.com>,
Gavin Hu <Gavin.Hu@arm.com>, nd <nd@arm.com>, nd <nd@arm.com>
Subject: [dpdk-dev] Questions on service core feature implementation
Date: Sat, 7 Mar 2020 01:14:38 +0000 [thread overview]
Message-ID: <VE1PR08MB51492476E7A7C68CBC2D06B998E00@VE1PR08MB5149.eurprd08.prod.outlook.com> (raw)
Hi Harry,
I have few observations on service core feature implementation.
I believe it is allowed to map/unmap a lcore to service while the service is running (i.e. not just during initialization stage). Please clarify otherwise.
Assuming yes -
In the 'service_run' function, the code to detect use of atomics seems to result in allowing the mt-unsafe service to run on multiple cores. Looking at the following code:
1 const int use_atomics = (service_mt_safe(s) == 0) &&
2 (rte_atomic32_read(&s->num_mapped_cores) > 1);
3 if (use_atomics) {
4 if (!rte_atomic32_cmpset((uint32_t *)&s->execute_lock, 0, 1))
5 return -EBUSY;
6
7 rte_service_runner_do_callback(s, cs, i);
8 rte_atomic32_clear(&s->execute_lock);
9 } else
10 rte_service_runner_do_callback(s, cs, i);
Let us say, on core1, after line 4, 'use_atomics' is set to 0. core1 is running the service function.
On the control plane let us say 'rte_service_map_lcore_set' is called to map the service to an additional core, core2.
Now, on core2, after line 4, 'use_atomics' is set to 1. But since core1 did not take execute_lock, core2 will take the lock and starts running the service function. This should not be allowed since the service is a mt-unsafe service.
Please let me know if my assessment is correct.
A possible solution is to take the execute_lock all the time.
Thank you,
Honnappa
next reply other threads:[~2020-03-07 1:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 1:14 Honnappa Nagarahalli [this message]
2020-03-10 12:52 ` Van Haaren, Harry
2020-03-10 16:06 ` Honnappa Nagarahalli
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=VE1PR08MB51492476E7A7C68CBC2D06B998E00@VE1PR08MB5149.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=Gavin.Hu@arm.com \
--cc=Phil.Yang@arm.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).