From: Ingo Molnar <mingo@elte.hu>
To: linux-kernel@vger.kernel.org
Subject: [patch] Real-Time Preemption, -RT-2.6.12-rc6-V0.7.47-20
Date: Tue, 7 Jun 2005 13:04:09 +0200 [thread overview]
Message-ID: <20050607110409.GA14613@elte.hu> (raw)
i have released the -V0.7.47-20 Real-Time Preemption patch, which can be
downloaded from the usual place:
http://redhat.com/~mingo/realtime-preempt/
i've implemented two new features:
- new debugging feature: CONFIG_DEBUG_RT_LOCKING_MODE, which
adds the /proc/sys/kernel/preempt_locks flag (default: 0). This way
the 'locking model' can be switched runtime - very useful for
debugging and profiling. Value 0 means that all spinlocks and rwlocks
are implemented via raw spinlocks/rwlocks. (which disable preemption,
increase latency, but improve throughput) Value 1 means the kernel
will fully preempt all locks again. (NOTE: the only safe runtime
switching of the locking model can be done while the system is idle,
so i've implemented the flag via two flags where the idle thread
propagates the new value from the user-flag to the kernel-flag. You
should put a "sleep 1" into scripts that switch the locking mode, to
guarantee that the new flag value is picked up.)
- performance feature: i've implemented a new scheduler feature called
'delayed preemption', which turns sync wakeups into guaranteed
wakeups, while preserving their workload-batching properties. A
delayed preemption request is implemented via the
TIF_NEED_RESCHED_DELAYED flag, which runs in parallel to the
"immediate preemption" TIF_NEED_RESCHED flag. If this works out fine
then it will be a suitable replacement for the upstream sync-wakeups
facility as well.
delayed preemption already improved the performance of 'hackbench' under
PREEMPT_RT quite signifiantly.
to build a -V0.7.47-20 tree, the following patches have 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-20
Ingo
next reply other threads:[~2005-06-07 11:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 11:04 Ingo Molnar [this message]
2005-06-07 11:31 ` [patch] Real-Time Preemption, -RT-2.6.12-rc6-V0.7.47-20 Steven Rostedt
2005-06-07 11:34 ` Ingo Molnar
2005-06-07 11:51 ` Michal Schmidt
2005-06-07 12:05 ` Ingo Molnar
2005-06-07 15:54 ` Esben Nielsen
2005-06-07 16:04 ` Ingo Molnar
2005-06-07 16:30 ` Michal Schmidt
2005-06-07 17:30 ` Peter Zijlstra
2005-06-07 19:05 ` Ingo Molnar
2005-06-07 19:02 ` Michal Schmidt
2005-06-07 19:25 ` Ingo Molnar
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=20050607110409.GA14613@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.