Greetings, From: http://www.xenomai.org/documentation/xenomai-2.3/pdf/Life-with-Adeos-rev-B.pdf
>The above behaviour is to be opposed to what happens with RTAI/LXRT for >instance, where threads migrating to the Linux space actually lose their >real- time priority in the same move, by inheriting the lowest priority >defined by the RTAI scheduler. I wished to understand what kind of advantages can it offer, and on a forum I found someone mentioning the following assumptions: - Threads don't spend much time in kernel space. - Thread in kernel space tend to hold resources that need to be released as quickly as possible. This does make sense to me. But then, from: http://www.xenomai.org/documentation/xenomai-2.3/pdf/Life-with-Adeos-rev-B.pdf > Xenomai threads are not only able to run over the context of the highest > priority domain in the pipeline (i.e. the primary domain) like kernelbased > Xenomai threads, but also in the regular Linux space (i.e. the secondary > domain), while still being considered as realtime by Xenomai, albeit > suffering higher scheduling latencies. Considering "Threads in kernel space tend to hold resources that need to be released as quickly as possible." what can be the reasons behind the design decision of letting the threads maintain their priority in user space in Xenomai? What kind of advantages does this behavior offer w.r.t hard real time? Please guide. -Anisha _______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
