All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: "PRADHAN, MAKARAND (RC-CA)" <makarand.pradhan@siemens.com>,
	"Xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] Interrupt latency close to 1ms on powerpc Xenomai 2.6.4
Date: Tue, 29 Sep 2015 18:15:52 +0200	[thread overview]
Message-ID: <560AB938.8090905@xenomai.org> (raw)
In-Reply-To: <B89CCBE86D4F62448EE4F6367C6D3C89221E4342@USMLVA0EM24MSX.ww017.siemens.net>

On 09/29/2015 06:04 PM, PRADHAN, MAKARAND (RC-CA) wrote:
>> Are you playing with the T_LOCK bit?
> 
> Yes. We do T_LOCK to lock the scheduler while we are in a critical section. Is that why the scheduler does not kick in immediately after the HW int?

If the IRQ happens while some task holds the scheduler lock, the answer
is yes, that is the point of it.

The scheduler lock is an ugly construct inherited from the dark ages of
RTOS. Xenomai being about properly emulating these for running legacy
code is the only reason why this anti-feature is present. I would
strongly recommend to use a mutual exclusion mechanism with a finer
granularity.

-- 
Philippe.


  reply	other threads:[~2015-09-29 16:15 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-29 15:35 [Xenomai] Interrupt latency close to 1ms on powerpc Xenomai 2.6.4 PRADHAN, MAKARAND (RC-CA)
2015-09-29 15:50 ` Philippe Gerum
2015-09-29 16:04   ` PRADHAN, MAKARAND (RC-CA)
2015-09-29 16:15     ` Philippe Gerum [this message]
2015-09-29 17:14       ` PRADHAN, MAKARAND (RC-CA)
2015-10-02 18:30         ` PRADHAN, MAKARAND (RC-CA)
2015-10-02 20:23           ` PRADHAN, MAKARAND (RC-CA)
2015-10-07 14:25             ` PRADHAN, MAKARAND (RC-CA)
2015-10-07 18:47               ` Philippe Gerum
2015-10-07 18:55                 ` Philippe Gerum
2015-10-07 19:27                   ` PRADHAN, MAKARAND (RC-CA)
2015-10-07 19:32                     ` Lennart Sorensen
2015-10-08  6:50                     ` Philippe Gerum
2015-10-08 14:43                       ` Lennart Sorensen
2015-10-08 14:52                         ` Gilles Chanteperdrix
2015-10-08 15:15                           ` Lennart Sorensen
2015-10-08 20:19                             ` Lennart Sorensen
2015-10-08 20:27                               ` Gilles Chanteperdrix
2015-10-08 20:30                                 ` Lennart Sorensen
2015-10-08 20:31                               ` Gilles Chanteperdrix
2015-10-08 20:41                                 ` Lennart Sorensen
2015-10-08 14:54                         ` Philippe Gerum
2015-10-08 15:05                           ` PRADHAN, MAKARAND (RC-CA)
2015-10-08 15:17                           ` Lennart Sorensen
2015-10-08 15:41                             ` Philippe Gerum
2015-10-08 15:47                               ` Gilles Chanteperdrix
2015-10-08 17:34                                 ` Philippe Gerum
2015-10-08 15:51                               ` Lennart Sorensen

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=560AB938.8090905@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=makarand.pradhan@siemens.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.