mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: linux-kernel@vger.kernel.org
Cc: Esben Nielsen <simlo@phys.au.dk>,
	Michal Schmidt <xschmi00@stud.feec.vutbr.cz>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: [patch] Real-Time Preemption, -RT-2.6.12-rc6-V0.7.47-29
Date: Tue, 7 Jun 2005 21:41:19 +0200	[thread overview]
Message-ID: <20050607194119.GA11185@elte.hu> (raw)


i have released the -V0.7.47-29 Real-Time Preemption patch, which can be 
downloaded from the usual place:

    http://redhat.com/~mingo/realtime-preempt/

it's a fixes and speedups release. Changes since -47-20:

 - x64 fixes (Michal Schmidt)

 - cpufreq fix (Esben Nielsen)

 - CONFIG_RT_DEADLOCK_DETECT build fix (Michal Schmidt)

 - MAX_USER_RT_PRIO fix (Steven Rostedt)

there are more microoptimizations to the spin_lock/unlock hotpath:

 - the caching of mutex_getprio() priority in p->normal_prio

 - the mutex lock/unlock paths are now all fall-through. (Found a gcc
   bug, it mishandles __builtin_expect() in certain cases and produces 
   correct but suboptimal code - we are working it around now.)

 - reduced the amount of recursive preemption-counter bumps via the use 
   of raw spinlocks

 - rely on the preemption-counter instead of IRQs-off sections

These changes brought the PREEMPT_RT overhead significantly down on 
hackbench workloads (clearly a worst-case test for PREEMPT_RT overhead).  

Would be interesting to see what kind of system time overhead PREEMPT_RT 
now causes for e.g. jack_test workloads.

to build a -V0.7.47-29 tree, the following patches should to be applied:

   http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.11.tar.bz2
   http://kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.12-rc6.bz2
   http://redhat.com/~mingo/realtime-preempt/realtime-preempt-2.6.12-rc6-V0.7.47-29

	Ingo

             reply	other threads:[~2005-06-07 19:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-07 19:41 Ingo Molnar [this message]
2005-06-07 20:31 ` Daniel Walker
2005-06-08  7:28   ` Ingo Molnar
2005-06-08  7:42     ` Ingo Molnar
2005-06-08  7:48       ` Ingo Molnar
2005-06-08 11:35         ` Gene Heskett
2005-06-08 11:59           ` Ingo Molnar
2005-06-08 14:54             ` Gene Heskett
2005-06-08 14:59               ` Ingo Molnar
2005-06-08 16:34                 ` Gene Heskett
2005-06-08 15:44         ` Daniel Walker

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=20050607194119.GA11185@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=simlo@phys.au.dk \
    --cc=xschmi00@stud.feec.vutbr.cz \
    /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

all inboxes | Powered by JetHome®