All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Nicolas BLANCHARD <n.blanchard@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: Rép. : Re: [Xenomai-help]  Switch mode with x86
Date: Wed, 29 Nov 2006 14:52:02 +0100	[thread overview]
Message-ID: <456D9082.5040409@domain.hid> (raw)
In-Reply-To: <s56d88c0.000@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]

Nicolas BLANCHARD wrote:
>>>>> "Nicolas BLANCHARD" <n.blanchard@domain.hid> 29.11 11:25 >>>
>> Hello,
>>
>> I've tested wiith Xenomai 2.3-rc2 (adeos 1.5-02)
>> and change the config : 
>>                                        - CONFIG_M586
>>                                        - disable CONFIG_INPUT_PCSPKR
> (it was on module)
>>                                        - disable prio boosting (check
> CONFIG_XENO_OPT_RPDISALBLE)
>> and it seems to work better, one hour without blocking, it's a record
>> for me.
>>
>> So, i will investigate to find which modification improve my problem.
> 
> After somes tests (kernel compil), it seems that prio boost is
> responsable of my
> problem. When it's disable (kernel option checked) my program run
> correctly.

Yeah, that's what I assumed now as well. Full output of
/proc/xenomai/sched would be interesting now.

> 
> I'm not sure to understand how the prio boost work.
> Can someone explain ?

Any Linux service, including those requested by Xenomai threads in
secondary mode, runs over the root thread. The root thread normally runs
at priority -1, i.e. below all Xenomai tasks. When
CONFIG_XENO_OPT_RPDISALBLE is *not* set and a Xenomai thread switches to
secondary mode, Xenomai raises the root thread's prio to the level of
that thread. This boosts Linux temporarily above any lower priority RT
thread, aiming at accelerating the completion of the requested Linux
service. If you do not depend on such boosting for your system design,
switching the service off improves the mode switch performance (and
obviously avoids a bug here we have to fix nevertheless).

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

       reply	other threads:[~2006-11-29 13:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <s56d88c0.000@domain.hid>
2006-11-29 13:52 ` Jan Kiszka [this message]
     [not found] <s575af89.064@domain.hid>
2006-12-05 17:15 ` Rép. : Re: [Xenomai-help] Switch mode with x86 Jan Kiszka
2006-12-05 12:33 Nicolas BLANCHARD
  -- strict thread matches above, loose matches on Subject: below --
2006-11-29 12:19 Nicolas BLANCHARD
2006-12-03 19:32 ` Jan Kiszka
2006-12-03 19:59   ` Philippe Gerum
2006-12-03 20:10     ` Jan Kiszka
2006-12-03 21:09     ` Jan Kiszka
2006-12-03 23:30       ` Philippe Gerum
2006-12-04  8:13         ` Jan Kiszka
2006-12-04 21:06           ` Jan Kiszka
2006-12-05 22:17             ` Philippe Gerum
2006-12-06  8:37               ` Jan Kiszka
2006-12-06  9:06                 ` Philippe Gerum
2006-12-05 22:18             ` Philippe Gerum
2006-12-04  9:46       ` Gilles Chanteperdrix
2006-12-03 21:02   ` Philippe Gerum
2006-11-29 10:25 Nicolas BLANCHARD
     [not found] <s56c97a4.096@domain.hid>
2006-11-28 20:27 ` Jan Kiszka
2006-11-28 19:09 Nicolas BLANCHARD

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=456D9082.5040409@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=n.blanchard@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.