From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: rolandtollenaar@domain.hid
Cc: RT <rwatollenaar@domain.hid>, Xenomai-help@domain.hid
Subject: Re: [Xenomai-help] ensuring code running in kernel modules has realtime priority
Date: Wed, 18 Jan 2012 11:52:04 +0100 [thread overview]
Message-ID: <4F16A454.5010602@domain.hid> (raw)
In-Reply-To: <4F167BD2.306@domain.hid>
On 01/18/2012 08:59 AM, RT wrote:
> Hi all,
>
> we have an interesting situation. We are using a module to do communication
> over a network (ethercat master module) to some remote IO.
>
> The ethercat module is loaded against the kernel in the normal manner.
>
> Now we possibly have overlooked that even though the call to the ethercat
> module (ioctl call) from our real-time application takes place in a xenomai
> real time task, the code of the ethercatmodule may be interrupted by other
> processes running on the machine. Due to the fact that the modules code is
> not running in any real-time prioritized space.
>
> If this is indeed the case, what would be the best or easiest manner to
> ensure that the module does not get interrupted, ie. to encapsulate it into
> the xenomai real-time priority sphere?
>
> Hope someone can point us in the right direction here. Its pretty urgent
> because the system is already running live and we are intermittently
> encountering this problem.
If I understand correctly, what you need is to rewrite the ethercat
driver as a real-time driver using the RTDM skin.
--
Gilles.
next prev parent reply other threads:[~2012-01-18 10:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 7:59 [Xenomai-help] ensuring code running in kernel modules has realtime priority RT
2012-01-18 10:52 ` Gilles Chanteperdrix [this message]
2012-01-20 15:31 ` Benner Bernd (MH/EES)
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=4F16A454.5010602@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=Xenomai-help@domain.hid \
--cc=rolandtollenaar@domain.hid \
--cc=rwatollenaar@domain.hid \
/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.