linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Shi <alex.shi@linaro.org>
To: peterz@infradead.org, mingo@redhat.com, corbet@lwn.net
Cc: linux-kernel@vger.kernel.org
Subject: [RFC PATCH 0/3] rtmutex comments update and trival fix
Date: Thu, 13 Apr 2017 22:02:51 +0800	[thread overview]
Message-ID: <1492092174-31734-1-git-send-email-alex.shi@linaro.org> (raw)

Also fix two little issues. This patchset tested by pi_stress, passed 
10G+ inversions.

$./pi_stress
Starting PI Stress Test
Number of thread groups: 7
Duration of test run: infinite
Number of inversions per group: unlimited
     Admin thread SCHED_FIFO priority 4
7 groups of 3 threads will be created
      High thread SCHED_FIFO priority 3
       Med thread SCHED_FIFO priority 2
       Low thread SCHED_FIFO priority 1
Current Inversions: 1051639657

Thanks
Alex
---
 Documentation/locking/rt-mutex-design.txt | 438 ++++++++++++++++++++---------------------------------------------
 Documentation/locking/rt-mutex.txt        |  32 ++---
 kernel/locking/rtmutex.c                  |  20 ++-
 3 files changed, 169 insertions(+), 321 deletions(-)

             reply	other threads:[~2017-04-13 14:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-13 14:02 Alex Shi [this message]
2017-04-13 14:02 ` [PATCH 1/3] rtmutex: comments update Alex Shi
2017-04-13 15:54   ` Steven Rostedt
2017-04-14  8:52     ` Alex Shi
2017-04-14 18:43       ` Steven Rostedt
2017-04-18  8:38         ` Alex Shi
2017-04-13 16:00   ` Steven Rostedt
2017-04-13 14:02 ` [PATCH 2/3] rtmutex: deboost priority conditionally when rt-mutex unlock Alex Shi
2017-04-13 14:23   ` Sebastian Siewior
2017-04-13 14:39   ` Peter Zijlstra
2017-04-13 16:09     ` Steven Rostedt
2017-04-13 16:21       ` Peter Zijlstra
2017-04-13 16:40         ` Steven Rostedt
2017-04-13 16:51           ` Peter Zijlstra
2017-04-13 14:02 ` [PATCH 3/3] rtmutex: remove unnecessary adjust prio Alex Shi
2017-04-13 16:15   ` Steven Rostedt

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=1492092174-31734-1-git-send-email-alex.shi@linaro.org \
    --to=alex.shi@linaro.org \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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).