public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: linux-kernel@vger.kernel.org
Subject: 2.6.19-rc6-rt5
Date: Mon, 20 Nov 2006 23:02:30 +0100	[thread overview]
Message-ID: <20061120220230.GA30835@elte.hu> (raw)

i've released the 2.6.19-rc6-rt5 tree, which can be downloaded from the 
usual place:

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

the -rt YUM repository for Fedora Core 6 can be activated via:

   cd /etc/yum.repos.d
   wget http://people.redhat.com/~mingo/realtime-preempt/rt.repo
   yum install kernel-rt

on x86_64, do:

   yum install kernel-rt.x86_64

lots of fixes and improvements were done to -rt5. In particular 
SMP/dual-core systems should get quite a bit faster. Changes:

 - implemented proper per-cpu page allocation (PCP-list) in 
   page_alloc.c, for PREEMPT_RT too. (previously this code was #ifdef-ed 
   out and we allocated straight from the zones - but this caused the 
   zone lock to act as a global lock)

 - speedup of PREEMPT_RT's implementation of atomic_dec_and_lock().
   (this was a major bottleneck for workloads like kernel compiles.)

 - more tracer features: symbolic stack backtraces embedded in 
   /proc/latency_trace for certain types of events, switchable syscall 
   tracing.

 - irq-threading cleanups, based on the comments from Sergei Shtylyov, 
   Daniel Walker and Benjamin Herrenschmidt.

 - vsyscall & tracing fixes: 'notsc' should not be required on the YUM 
   rpms anymore.

to build a 2.6.19-rc6-rt5 tree, the following patches should be applied:

  http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.18.tar.bz2
  http://kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.19-rc6.bz2
  http://redhat.com/~mingo/realtime-preempt/patch-2.6.19-rc6-rt5

as usual, bugreports, fixes and suggestions are welcome,

	Ingo

             reply	other threads:[~2006-11-20 22:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-20 22:02 Ingo Molnar [this message]
2006-11-20 22:39 ` 2.6.19-rc6-rt5 Alistair John Strachan
2006-11-21  7:17   ` 2.6.19-rc6-rt5 Ingo Molnar
2006-11-20 23:18 ` 2.6.19-rc6-rt5 Alistair John Strachan
2006-11-21  7:20   ` 2.6.19-rc6-rt5 Ingo Molnar
2006-11-21  1:35 ` 2.6.19-rc6-rt5 Sergio Monteiro Basto
2006-11-21  8:04   ` 2.6.19-rc6-rt5 Ingo Molnar
2006-11-21  3:07 ` compile problems 2.6.19-rc6-rt5 Sergio Monteiro Basto
2006-11-21  7:43   ` Ingo Molnar
2006-11-21  7:54   ` Ingo Molnar
2006-11-22 11:37 ` 2.6.19-rc6-rt5 Robert Schwebel
2006-11-23 20:43   ` 2.6.19-rc6-rt5 Eduardo Valentin
2006-11-23 21:11     ` 2.6.19-rc6-rt5 Robert Schwebel
2006-11-22 14:06 ` 2.6.19-rc6-rt5 Mark Knecht
2006-11-28 17:33   ` 2.6.19-rc6-rt5 Lee Revell
2006-11-28 19:53     ` 2.6.19-rc6-rt5 Mark Knecht
2006-11-28 20:16       ` 2.6.19-rc6-rt5 Lee Revell
2006-11-28 20:15     ` 2.6.19-rc6-rt5 Ingo Molnar
2006-11-28 22:52       ` 2.6.19-rc6-rt5 Mark Knecht
2006-11-29  6:54         ` 2.6.19-rc6-rt5 Ingo Molnar
2006-11-26 14:39 ` 2.6.19-rc6-rt5 Karsten Wiese
2006-11-27  7:48   ` 2.6.19-rc6-rt5 Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2006-11-21 12:01 2.6.19-rc6-rt5 Marcus Hartig
2006-11-21 12:45 ` 2.6.19-rc6-rt5 Karsten Wiese
2006-11-25 22:01 2.6.19-rc6-rt5 Thomas

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=20061120220230.GA30835@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.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