From: Thomas Gleixner <tglx@linutronix.de>
To: Kirill Tkhai <tkhai@yandex.ru>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Mike Galbraith <umgwanakikbuti@gmail.com>
Subject: Re: [RFC] rtmutex: Do not boost fair tasks each other
Date: Wed, 28 May 2014 22:26:56 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.10.1405282157100.3952@nanos> (raw)
In-Reply-To: <1399314660.6978.3.camel@localhost.localdomain>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 613 bytes --]
On Mon, 5 May 2014, Kirill Tkhai wrote:
> В Сб, 03/05/2014 в 20:54 +0200, Thomas Gleixner пишет:
> > Though exercising that code path as much as we can is not a bad thing
> > either. So I'd like to see that made compile time conditional on one
> > of the lock testing CONFIG items.
>
> +#ifndef CONFIG_RT_MUTEX_BOOST_ALL
No, not another pointless config option. Read what I said. What's
wrong with using an existing config item, e.g DEBUG_RT_MUTEXES?
> +#define heritable_prio(prio) (rt_prio(prio) || dl_prio(prio))
inheritable please. It's not priority heritance and never will be.
Thanks,
tglx
next prev parent reply other threads:[~2014-05-28 20:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 9:21 Kirill Tkhai
2014-05-03 18:54 ` Thomas Gleixner
2014-05-04 7:17 ` Peter Zijlstra
2014-05-04 12:13 ` Thomas Gleixner
2014-05-05 18:31 ` Kirill Tkhai
2014-05-28 20:26 ` Thomas Gleixner [this message]
2014-05-29 20:52 ` Kirill Tkhai
2014-06-17 14:19 ` Kirill Tkhai
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.DEB.2.10.1405282157100.3952@nanos \
--to=tglx@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paul.gortmaker@windriver.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tkhai@yandex.ru \
--cc=umgwanakikbuti@gmail.com \
/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
Powered by JetHome