From: Jan Kiszka <jan.kiszka@domain.hid>
To: "Stolz, Stefan, PGR2" <Stefan.Stolz@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] scheduling of rtdm-handler
Date: Thu, 24 May 2007 10:05:51 +0200 [thread overview]
Message-ID: <4655475F.7040002@domain.hid> (raw)
In-Reply-To: <C0662F7F2A8A974FAA140822A2336BF0F173EC@deimsg10.de.net.world>
[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]
Stolz, Stefan, PGR2 wrote:
> Hello,
>
> i'm developing a rt-driver for the rtdm with Xenomai and i've got one
> question.
> how are the handler-functions (like rtdm_read_handler,
> rtdm_write_handler, ...) scheduled if there are other rt-tasks?
> e.g. i've got the rtdm-driver which handles read and write (read and
> write have to do some i/o-operations) and a two other rt-tasks. What
> happens if the task with the lower priority uses the rtdm-driver to read
> and write data and the task with the higher priority want's to run. Are
> the i/o-operations peempted by the high priority task? If it is so, is
> it possible to give the driver a higher priority or do i have to create
> a task with a higher priority in the driver?
RTDM device handlers run in the context of the caller, i.e. some RT (or
also non-RT) task. Thus, they are schedule like the caller - unless you
apply locking mechanisms like spinlocks which block preemption for a
while or mutexes which may cause priority boosts if contention with
tasks of higher priority occur.
Additionally, there are IRQ handlers which run at highes priority and
RTDM kernel tasks which can be set to custom RT priorities.
No black magic here, it's all standard OS design.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
prev parent reply other threads:[~2007-05-24 8:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 14:41 [Xenomai-help] scheduling of rtdm-handler Stolz, Stefan, PGR2
2007-05-24 8:05 ` 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=4655475F.7040002@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=Stefan.Stolz@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.