linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin Däumler" <mdae@cs.tu-chemnitz.de>
To: linux-rt-users@vger.kernel.org
Subject: Re: Priority Inheritance per se?
Date: Tue, 14 Sep 2010 13:12:13 +0200	[thread overview]
Message-ID: <4C8F588D.2080308@cs.tu-chemnitz.de> (raw)
In-Reply-To: <4C8F46B1.1010804@disco.unimib.it>

Sergio Ruocco wrote:

> before really deciding for the use of PI, you may want to read what
> Victor Yodaiken had to say:
>
> http://www.yodaiken.com/papers-and-talks/
> Against priority inheritance, Victor Yodaiken. September 23, 2004
> http://www.yodaiken.com/papers/inherit.pdf
>
> Here is a general Linux RT workshop report, with some comments on PI:
> http://lwn.net/Articles/354690/


Hi Sergio,

thanks for that reading. I (hope to) know which drawbacks and
shortcomings priority inheritance has. Before I can make a
decision about using an RT_PREEMPT patched Linux, I want to
know if the RT_PREEMPT-patch introduces priority inheritance
automatically, that is, without using any locks?

For example (from my opening post):

Imagine a hypothetical case: a high RT-priority (60) task
triggers a blocking system call which triggers a device driver
whose ISR is a kernel thread with RT-priority 49. So, a medium
RT-priority (55) task is able block the high RT-priority task,
isn't it?


With kind regards,
Martin Däumler
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2010-09-14 11:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-10  6:49 Priority Inheritance per se? Martin Däumler
2010-09-14  9:56 ` Sergio Ruocco
2010-09-14 11:12   ` Martin Däumler [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=4C8F588D.2080308@cs.tu-chemnitz.de \
    --to=mdae@cs.tu-chemnitz.de \
    --cc=linux-rt-users@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).