linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Nicholas Mc Guire <der.herr@hofr.at>
Cc: linux-rt-users@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Andreas Platschek <platschek@ict.tuwien.ac.at>
Subject: Re: [PATCH] migrate_disable pushd down in rt_read_trylock
Date: Fri, 29 Nov 2013 16:14:01 +0100	[thread overview]
Message-ID: <20131129151401.GD31099@linutronix.de> (raw)
In-Reply-To: <20131123005158.GA16338@opentech.at>

* Nicholas Mc Guire | 2013-11-23 01:51:58 [+0100]:

>>From 5c9a0c1510ec29c1e148f66f3c111f52f7565df1 Mon Sep 17 00:00:00 2001
>From: Nicholas Mc Guire <der.herr@hofr.at>
>Date: Fri, 22 Nov 2013 02:41:48 -0500
>Subject: [PATCH] migrate_disable pushd down in rt_read_trylock
>
> No need to migrate_disable before requesting the lock and no need to 
> speculatively disable/enable on every recursive call. migration_disable 
> can be done at the latest point in the code before returning an acquired 
> ``lock.
>
> patch is on top of 3.12-rt2
>
> No change of functionality
Applied without this line.

>Signed-off-by: Nicholas Mc Guire <der.herr@hofr.at>

Sebastian

  reply	other threads:[~2013-11-29 15:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-23  0:51 [PATCH] migrate_disable pushd down in rt_read_trylock Nicholas Mc Guire
2013-11-29 15:14 ` Sebastian Andrzej Siewior [this message]
2013-11-29 15:44   ` Sebastian Andrzej Siewior
2013-11-30  2:30     ` Nicholas Mc Guire
2013-11-30  6:47       ` Nicholas Mc Guire
2013-12-15 13:16         ` Sebastian Andrzej Siewior
2013-12-15 14:15           ` Nicholas Mc Guire
2013-12-15 15:06             ` Sebastian Andrzej Siewior

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=20131129151401.GD31099@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=der.herr@hofr.at \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=platschek@ict.tuwien.ac.at \
    --cc=rostedt@goodmis.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).