All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Rodrigo Rosenfeld Rosas <lbocseg@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Have condition variables Priority Inheritance Protection (PIP)?
Date: Wed, 03 May 2006 09:57:16 +0200	[thread overview]
Message-ID: <4458625C.5020808@domain.hid> (raw)
In-Reply-To: <200605020936.00576.lbocseg@domain.hid>

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

Rodrigo Rosenfeld Rosas wrote:
> Em Sexta 28 Abril 2006 17:42, Jan Kiszka escreveu:
> 
>> ...
>>> Could someone please point me the reason?
>> Just as with semaphores: there is no ownership concept for condition
>> variables. Thus, who should be boosted to your priority in case you
>> decide to wait on such a resource?
> 
> Sorry, you are right. Xenomai has no way of knowing which tasks could signal 
> the condition variable. If I wanted to wait on some resource using priority 
> inheritance I guess I would have to raise the priority of the task owning the 
> resource manually when only one task can signal the condition variable (or 
> semaphore). Do you know other better approaches? I mean if a task A of 
> priority 50, shares a resource with task B and C, both priority 10 through 
> semaphores. Suppose B and C are using the semaphore when A requests it. How 
> could they be boosted to A's priority, so that A is protected with priority 
> inheritance and then go back to their original priorities? Or should I use 
> other IPC mechanism for sharing resource with PIP?

Mutexes were invented for such resource access control :). They have a
strict ownership concept, thus allowing to apply PIP as well.

Jan


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

  reply	other threads:[~2006-05-03  7:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-28 20:36 [Xenomai-help] Have condition variables Priority Inheritance Protection (PIP)? Rodrigo Rosenfeld Rosas
2006-04-28 20:42 ` Jan Kiszka
2006-05-02 12:36   ` Rodrigo Rosenfeld Rosas
2006-05-03  7:57     ` Jan Kiszka [this message]
2006-05-03 16:15       ` Rodrigo Rosenfeld Rosas
2006-05-04  6:54         ` Jan Kiszka
2006-05-04 13:58           ` Rodrigo Rosenfeld Rosas

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=4458625C.5020808@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=lbocseg@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.