linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Stanislav Meduna <stano@meduna.org>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: Priority inheritance?
Date: Tue, 30 Oct 2012 00:38:27 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.02.1210300035500.2756@ionos> (raw)
In-Reply-To: <508E7DF2.1040301@meduna.org>

On Mon, 29 Oct 2012, Stanislav Meduna wrote:
> Can I leave the low-prio threads at SCHED_OTHER and rely on
> the PTHREAD_PRIO_INHERIT to boost their priority in case they
> were preempted with the lock held and the RT-thread needs
> to lock it too

That's how priority inheritance is defined. In case of contention the
lock owner inherits the scheduling class and the priority of the
(higher class/priority) contender.

Thanks,

	tglx

      reply	other threads:[~2012-10-29 23:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-29 13:00 Priority inheritance? Stanislav Meduna
2012-10-29 23:38 ` Thomas Gleixner [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=alpine.LFD.2.02.1210300035500.2756@ionos \
    --to=tglx@linutronix.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=stano@meduna.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).