All of lore.kernel.org
 help / color / mirror / Atom feed
From: "M. Koehrer" <mathias_koehrer@domain.hid>
To: rpm@xenomai.org, mathias_koehrer@domain.hid
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Scheduler: Strange priority handling
Date: Mon, 14 May 2007 13:57:50 +0200 (CEST)	[thread overview]
Message-ID: <9958525.1179143870179.JavaMail.ngmail@domain.hid> (raw)
In-Reply-To: <1179136852.5045.76.camel@domain.hid>

HI all,

thanks for all the responses.
Using mutexes instead of semaphores actually solves the issue.
However, the API documentation of rt_sem_create() is a little bit confusing here.
The "mode" parameter of rt_sem_create() may contain "S_PRIO" which 
"makes tasks pend in priority order on the semaphore".
I interpret this that it works actually the very same as with mutexes. However, it
is implemented that sem_v directly triggers a waiting task (even if it is low prio).
As the semaphore has nothing to do with the scheduler, this makes sense.
However, this cannot be found within the API documentation.

Regards

Mathias

-- 
Mathias Koehrer
mathias_koehrer@domain.hid


Viel oder wenig? Schnell oder langsam? Unbegrenzt surfen + telefonieren
ohne Zeit- und Volumenbegrenzung? DAS TOP ANGEBOT JETZT bei Arcor: günstig
und schnell mit DSL - das All-Inclusive-Paket für clevere Doppel-Sparer,
nur  39,85 €  inkl. DSL- und ISDN-Grundgebühr!
http://www.arcor.de/rd/emf-dsl-2


  reply	other threads:[~2007-05-14 11:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-14  8:40 [Xenomai-help] Scheduler: Strange priority handling with multiple tasks waiting for one semaphore M. Koehrer
2007-05-14  9:42 ` Dmitry Adamushko
2007-05-14  9:45 ` Jan Kiszka
2007-05-14 10:00 ` Philippe Gerum
2007-05-14 11:57   ` M. Koehrer [this message]
2007-05-14 12:14     ` [Xenomai-help] Scheduler: Strange priority handling Dmitry Adamushko
2007-05-14 12:17     ` 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=9958525.1179143870179.JavaMail.ngmail@domain.hid \
    --to=mathias_koehrer@domain.hid \
    --cc=rpm@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.