[Xenomai] copperplate/registry daemon connection failure
ronny.meeus at gmail.com
Fri Jan 6 10:54:40 CET 2017
On Fri, Jan 6, 2017 at 10:29 AM, Philippe Gerum <rpm at xenomai.org> wrote:
> On 01/06/2017 10:21 AM, Ronny Meeus wrote:
>> That logic I had seen before.
>> As I understand the code it just tries 3 times to connect to the daemon
>> and if not successful, it just tries to start it again and reconnects ...
>> I find it a strange logic just to try something 3 times and hope it
>> will succeed.
>> In our case the CPU is fully loaded with RT threads so my assumption is that
>> the daemon, running at nonRT prio will not be scheduled at all.
>> (also see the traces above that confirm my assumptions)
>> I would expect to see some kind of synchronization mechanism between the
>> daemon and the application.
> The point is that such init code is aimed at running early, prior to any
> Xenomai application code, this is cold bootstrap code. The fact that
> your app can spawn threads overconsuming the CPU earlier than Xenomai's
> basic init code is a problem for Xenomai.
on our system we have a lot of Xenomai applications running, it can be up to 10
or more. So it is impossible to guarantee that there will be CPU power available
at the moment Xenomai init is called.
Next to the application code also the Linux kernel threads can consume a lot of
CPU power (especially during init).
Xenomai applications can be started during init but also at runtime, so it is
impossible to make assumptions about the availability of CPU power.
More information about the Xenomai