From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: aking <jinxin16897123@163.com>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] Real Time about user thread
Date: Mon, 29 Jul 2013 00:19:55 +0200 [thread overview]
Message-ID: <51F5990B.9010600@xenomai.org> (raw)
In-Reply-To: <51F3B976.3020802@163.com>
On 07/27/2013 02:13 PM, aking wrote:
> Hi,all
Hi,
> RTDM is in the xenoami domain ,
A thread or an interrupt can be in the xenomai or linux domain, but RTDM
is a skin, so, it does not really make sense to say that it is in the
xenomai domain. RTDM allows to create real-time threads or to register
interrupt handlers which can be executed in the Xenomai domain, but also
allows defining callback executed in Linux domain.
> and it's driven by the IRQ so that could provide hard real time.
RTDM is no more driven by IRQ than the Linux kernel is driven by IRQ,
and this is not sufficient to provide hard real-time (otherwise, the
Linux kernel would provide hard real-time). The mechanism allowing hard
real-time response to interrupts is the so-called "Optimistic interrupt
protection" scheme, see [1] for more details.
> The userspace thread is in Linux domain(maybe?)
Or maybe not, see above.
, what mechanism
> was implemented to provide a Linux userspace thread real time?
> Thank you very much.
>
Xenomai uses the Adeos patch to allow executing user-space threads in
Xenomai domain, see [1] for more detains, and implements the classic
real-time scheduling policies, aka SCHED_FIFO and SCHED_RR to provide
deterministic scheduling.
[1]
http://www.xenomai.org/documentation/branches/v2.3.x/pdf/Life-with-Adeos-rev-B.pdf
--
Gilles.
prev parent reply other threads:[~2013-07-28 22:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-27 12:13 [Xenomai] Real Time about user thread aking
2013-07-28 22:19 ` Gilles Chanteperdrix [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=51F5990B.9010600@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=jinxin16897123@163.com \
--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.