All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>,
	Bosko Radivojevic <bosko.radivojevic@domain.hid>
Cc: xenomai-help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Handling irq
Date: Fri, 21 Mar 2008 12:10:38 +0100	[thread overview]
Message-ID: <47E397AE.2010009@domain.hid> (raw)
In-Reply-To: <2ff1a98a0803210354g40137eeds72eb742142856cd@domain.hid>

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

Gilles Chanteperdrix wrote:
> On Fri, Mar 21, 2008 at 11:50 AM, Bosko Radivojevic
> <bosko.radivojevic@domain.hid> wrote:
>> I have much better results using rtdm_lock_get_irqsave and
>>  rtdm_lock_put_irqrestore. I hope this is the "appropriate method" of
>>  doing it :)
>>
>>  Thanks!
> 
> Shutting interrupts off for long periods of time is not a good idea:
> - it does not scale well, since it does not work for more than one task;
> - it kills the precision of timers by delaying the timer interrupt.
> And I am sure we can find many more drawbacks.

- it only reduces the probability of your problem, it doe not
   eliminate it completely

You can still be interrupted right after task wakeup, before 
rtdm_lock_get_irqsave. And there is still the possibility to be delayed 
by interrupts BEFORE your task is even triggered.

If you cannot live with this conceptual jitter (which you'll find on any 
RTOS with more than one job running), you have to do ahead-of-time 
scheduling with busy waiting until the actual release date. That will 
mean disabling IRQs for a really long time + burning a lot of CPU power. 
Kind of last resort, not generally recommended.

Jan


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

      reply	other threads:[~2008-03-21 11:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-18 12:27 [Xenomai-help] Handling irq Bosko Radivojevic
2008-03-18 14:23 ` Gilles Chanteperdrix
2008-03-19 11:10   ` Bosko Radivojevic
2008-03-19 20:58     ` Gilles Chanteperdrix
2008-03-20  9:31       ` Bosko Radivojevic
2008-03-21 10:50       ` Bosko Radivojevic
2008-03-21 10:54         ` Gilles Chanteperdrix
2008-03-21 11:10           ` Jan Kiszka [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=47E397AE.2010009@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=bosko.radivojevic@domain.hid \
    --cc=gilles.chanteperdrix@xenomai.org \
    --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.