All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Charles Clerdan <charles.clerdan@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Some questions about Xenomai
Date: Fri, 25 Jun 2010 14:12:59 +0200	[thread overview]
Message-ID: <4C249D4B.7000303@domain.hid> (raw)
In-Reply-To: <AANLkTikA0fz6Rt8-4NqaOGL7_b_UdbVzSXCRYxg8J68h@domain.hid>

Charles Clerdan wrote:
> And a last one (for now ...), I read here  :-
> http://www.xenomai.org/documentation/branches/v2.3.x/pdf/Native-API-Tour-rev-C.pdf
> that :
> /"When a realtime
> task executes into the Linux domain on a given processor, the
> Linux kernel as a whole inherits the realtime
> priority of such task, and thus
> competes for the CPU resource by priority with other realtime
> tasks regardless of
> the domain (i.e. Linux or Xenomai) they happen to belong to. In other
> words, the
> realtime
> priority scheme enforced by the native API is consistent across domains. "/
> 
> I was thinking that Linux were a process of Xenomai with the lowest
> effective priority, and a task in secondary mode were only in
> competition with the others Linux threads (or others Xenomai thread in
> 2ndary mode). But if I'm wrong, how can the 2 schedulers share
> ressources in order to keep a hard real-time behaviour (at less for
> Xenomai tasks in 1st mode).

I am not sure I understand your question.

The two schedulers do not share ressources. What is meant by this
sentence is that the Linux kernel is a task, from Xenomai scheduler's
point of view, and this tasks inherits the priority of Xenomai tasks
running in secondary mode. The Linux scheduler is not involved.

And giving to a task running in secondary mode a priority higher than a
task running in primary mode looks like a design error anyway.

If you do not like this behaviour, you can disable it, but, on the whole
it makes things a little more natural.

-- 
					    Gilles.


  reply	other threads:[~2010-06-25 12:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-24  7:30 [Xenomai-help] Some questions about Xenomai Charles Clerdan
2010-06-24  8:58 ` Gilles Chanteperdrix
2010-06-24  9:10   ` Charles Clerdan
2010-06-24 19:29 ` Gilles Chanteperdrix
     [not found]   ` <AANLkTimofdDy_OSC6dr_2l4X8vAn8oPsQdqVXrSWZ-2e@domain.hid>
2010-06-25  7:42     ` Charles Clerdan
2010-06-25 12:12       ` Gilles Chanteperdrix [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-08-03 16:03 Martin Kremenak
2010-08-03 16:26 ` Philippe Gerum

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=4C249D4B.7000303@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=charles.clerdan@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.