From: Jan Kiszka <jan.kiszka@domain.hid>
To: tstratman@domain.hid
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Bottom half task scheduling
Date: Sun, 12 Sep 2010 10:53:57 +0200 [thread overview]
Message-ID: <4C8C9525.1060101@domain.hid> (raw)
In-Reply-To: <7301cc886b22b37fcbc8cda61c515d07.squirrel@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]
Am 11.09.2010 22:08, Travis Stratman wrote:
> Hello,
>
> I am writing a Xenomai driver with an interrupt that must trigger a
> complex series of hardware accesses that may not be atomic (i.e. waiting
> for DMA to complete). I'd like to move this section to a bottom half. In a
> Linux driver I would use a workqueue but I haven't been able to determine
> what the preferred method would be in Xenomai. All of the task creation
> API that I have considered cannot be called from an interrupt handler as
> they may reschedule.
Simply create the RTDM task(s) in advance. Creating tasks on demand and
in IRQ context would be crazy.
At this chance, also start thinking about what priorities you want to
assign to them (typically the harder part of the design).
>
> Can anyone point me to some documentation or example that covers this? Any
> pointers would be appreciated.
RTnet uses RTDM tasks quite heavily. But its code base is large, and not
all usages are really good examples anymore.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2010-09-12 8:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-11 20:08 [Xenomai-help] Bottom half task scheduling Travis Stratman
2010-09-11 20:26 ` Gilles Chanteperdrix
2010-09-12 2:49 ` Travis Stratman
2010-09-12 8:53 ` Jan Kiszka [this message]
2010-09-12 13:42 ` Travis Stratman
2010-09-12 13:48 ` Jan Kiszka
2010-09-12 14:13 ` Travis Stratman
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=4C8C9525.1060101@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=tstratman@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.