Re: [Xenomai] Simple application for invoking rtdm driver

[Philippe Gerum <rpm@xenomai.org>]

On 03/27/2018 02:09 PM, Pintu Kumar wrote:
> Hi,
> 
> Thank you so much for all your explanation.
> But, before I dig deeper, I have some simple questions which is troubling me.
> 
> 1) In Idle case, we see latency improvement (~2-3 micro-seconds on
> average) using Xenomai native task application, compared to normal
> posix thread application (with 100 us sleep).
>     Then why not it is seen with RTDM driver and its application ?
> 
> 2) In the idle case itself, we have seen read/write latency
> improvement using RTNET (loopback) and simple UDP client/server
> application using Xenomai posix skin
>     Then why not same is visible with RTDM driver?
>

All answers have already been given, or can be inferred fairly easy from
what was said earlier.

On a general note, it is safer not to compare apples and oranges when it
comes to benchmarking: two different codes usually do things
differently, so you may simply not be measuring the same work load. If
you really want to figure out what happens, you may need to dive into
the implementation.

> 3) How to choose, when to develop a Xenomai native application, and
> when to simply convert using posix skin ?
> 

Choose portability with POSIX. The so-called "native" - now Alchemy API
- was defined 14 years ago for a single purpose: make greybards coming
from the traditional RTOS world comfortable with API semantics close to
what they were used to with VxWorks, VRTX, pSOS and friends.

Alchemy exists in Xenomai 3 only for the purpose of making the life of
people migrating from 2.x easier.

-- 
Philippe.