From: Philippe Gerum <rpm@xenomai.org>
To: Jeff Webb <jeff.webb@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Xenomai vs. RTLinux
Date: Fri, 10 Mar 2006 15:36:12 +0100 [thread overview]
Message-ID: <44118EDC.2010003@domain.hid> (raw)
In-Reply-To: <440F5F23.7000703@domain.hid>
Jeff Webb wrote:
>
<snip>
> The worst-case scheduling latency for the xenomai user-space application
> was only a few microseconds worse than the kernel-space version. Is
> this what you would expect?
>
Usually, yes. The gap may increase on low-end systems though, especially for those
exhibiting unfriendly cache behaviour for instance. But the worst-case latency is
still predictable, albeit higher.
> I did not do a very thorough test with my interrupt handler, but the
> results seemed similar to what I described above for the scheduler. Is
> there a big penalty in terms of worst-case latency for user-space
> interrupt handlers that I may not have seen? I'm just looking for any
> major problems that I might encounter if we port our real-time
> applications to user-space.
>
> Is RTLinuxPro's PSDD (user-space) development environment similar to
> xenomai's user-space real-time threads? Any known
> advantages/disadvantages to either system?
My knowledge of PSDD being limited to the contents of the press releases, which
are the services PSDD provides to applications, roughly?
>
> We currently use C and FORTRAN in our RTLinuxFree modules, and would
> like to be able to add C++ and FORTRAN as well. Are there any problems
> you see with using these languages in xenomai user-space real-time
> programs?
None, provided your runtime environment can invoke callouts written in C in order
to start Xenomai system calls. Those syscalls use the very same channel to
re-enter the kernel than normal Linux system calls.
>
> Is there planned support for native AMD x86_64 support? We have several
> of these machines on our desktops and would like to upgrade our HWIL
> machines as well.
Not planned, yet.
>
> We are also concerned about "future-proofing" as someone else put it the
> other day. I hope that xenomai will not suffer the fate of RTLinuxFree
> in a few years. Of course, I understand there are no guarantees. Do
> you see any advantages to xenomai over RTLinuxPro in this respect?
>
I would rephrase your question this way: "what would prevent Xenomai from becoming
a proprietary technology?". Short answer: critical pieces of the Xenomai codebase
bear various GPL copyrights from different people or organizations having very
little or no common interests, aside of keeping Xenomai free, that is. Another
form of the famous "divide and conquer" approach.
> Another issue is technical support and documentation. The xenomai
> documentation seems good enough to me, although it sounds like
> RTLinuxPro is quite a bit more substantial. It also looks like the
> developers on this list are very responsive and helpful, but I don't
> know how that compares to what we would get from FSMLabs. Any input on
> these topics?
>
> It appears that xenomai is released under the LGPL and can be used with
> proprietary applications. Although our simulations are just for
> internal use, and I would always advocate releasing free software, I was
> wondering if xenomai is subject to the RTLinux patent, or if it uses a
> different process.
My answer must be awfully biased, but:
http://www.linuxdevices.com/news/NS7320885236.html
>
> My first impression of xenomai is very positive. I like the clean API,
> and the user-space real-time would make life *much* nicer for me. I'm
> glad there is a such nice piece of free software available for real-time
> programming under GNU/Linux. Thanks!
>
You are definitely welcome.
> Thank you for taking the time to read these questions and comments. Any
> comments or testimonies regarding xenomai or RTLinuxPro would be
> appreciated.
>
> Thanks again,
>
> Jeff Webb
>
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
>
--
Philippe.
next prev parent reply other threads:[~2006-03-10 14:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 22:48 [Xenomai-help] Xenomai vs. RTLinux Jeff Webb
2006-03-09 0:44 ` Christopher Stone
2006-03-09 0:58 ` Jan Kiszka
2006-03-09 14:48 ` Rodrigo Rosenfeld Rosas
2006-03-09 15:03 ` Gilles Chanteperdrix
2006-03-09 16:31 ` Rodrigo Rosenfeld Rosas
2006-03-09 18:02 ` Jeff Webb
2006-03-09 18:19 ` Gilles Chanteperdrix
2006-03-30 16:22 ` [Xenomai-core] AMD x86_64 support Jeff Webb
2006-03-09 0:47 ` [Xenomai-help] Xenomai vs. RTLinux Jan Kiszka
2006-03-09 8:08 ` Heikki Lindholm
2006-03-10 14:36 ` Philippe Gerum [this message]
2006-03-10 17:07 ` Jeff Webb
2006-03-10 20:33 ` Dmitry Adamushko
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=44118EDC.2010003@domain.hid \
--to=rpm@xenomai.org \
--cc=jeff.webb@domain.hid \
--cc=xenomai@xenomai.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.