From: Jan Kiszka <jan.kiszka@domain.hid>
To: ramoncostacastello@domain.hid
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] native kernel task example
Date: Thu, 13 May 2010 11:06:33 +0200 [thread overview]
Message-ID: <4BEBC119.4070408@domain.hid> (raw)
In-Reply-To: <4BEBB838.2080407@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1300 bytes --]
Ramon wrote:
> Hi,
>
> I have a system developed (teaching and research purposes) developed in
> RTLinuxfree and currently I'm trying to migrate
> this system to Xenomai (several task periodical task with period of
> 100us (one at 50us)).
> As a first step I would like to run them at kernel level to preserve
> performance (hard realtime),
Unless your system is already running on its limits with this 20 KHz
job, kernel vs. user space won't make the big difference. Check the
results of the latency test while loading the system with I/O and memory
cache stress to get a first impression.
> latter I will try to migrate
> user space.
Specifically while trying to stabilize the port, you will quickly love
the robustness of user space: if something crashes or hangs, just attach
gdb - but don't forget to enable the Xenomai watchdog in order to catch
runaway tasks.
>
> This task contains low level commands (out, in commands to access AD/DA
> card registers)
iopl(3) will grant your root user space process in/out privileges. Not
nice, but probably easier as a first step than porting over the Analogy
framework.
Jan
PS: Specifically for educational purposes, it is a bad idea to continue
spreading the legacy concept of kernel-based RT applications.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
prev parent reply other threads:[~2010-05-13 9:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 20:05 [Xenomai-help] native kernel task example Ramon
2010-05-12 20:26 ` Wolfgang Grandegger
2010-05-12 21:22 ` Jan Kiszka
2010-05-13 8:28 ` Ramon
2010-05-13 9:06 ` Jan Kiszka [this message]
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=4BEBC119.4070408@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=ramoncostacastello@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.