From: John Richard Moser <nigelenki@comcast.net>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 2.6.16-rc6-rt1
Date: Wed, 15 Mar 2006 11:25:38 -0500 [thread overview]
Message-ID: <44184002.4010109@comcast.net> (raw)
In-Reply-To: <20060312220218.GA3469@elte.hu>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
So Ingo, when are we going to see these in the mainline kernel yet? I
am particularly interested in priority inheriting semaphores; it seems
like brain damage to have something spin_lock() and block a higher
priority process while other mid-priority processes (i.e. higher than
the blocker but lower than the blocked) are given execution priority.
As I understand, the PI code fixes this by inheriting the priority of
the highest blocked process on a lock into whatever process is holding
the lock, which sounds like exactly what should be happening.
Ingo Molnar wrote:
> i have released the 2.6.16-rc6-rt1 tree, which can be downloaded from
> the usual place:
>
> http://redhat.com/~mingo/realtime-preempt/
>
> again, lots of changes all over the map:
>
> - firstly, the -rt tree has been rebased to 2.6.16-rc6, which was a more
> complex operation than usual, due to the many changes in 2.6.16 (in
> particular the mutex code).
>
> - the PI code got reworked again, this time by Thomas Gleixner. The
> priority boosting chain is now instantaneous again (and not
> wakeup/scheduling based) - but the previous list-walking hell has been
> avoided via the clever use of plists. Plus many other changes and
> lots of cleanups to the rt-mutex proper.
>
> - the rt-SLAB code got reworked too - hopefully for the better.
>
I have not heard anything about your SLAB code before. Think you can
give me a basic idea of what it's supposed to do?
> - there's also a completely new PI-futex approach included, ontop of the
> robust-list futex feature. All combinations of PI and robustness are
> supported: default non-robust non-PI futexes, robust+PI, !robust+PI,
> PI+!robust futexes.
>
I don't know what non-robust futex means. Also don't you mean
!robust+!PI (00), robust+PI (11), !robust+PI (01), robust+!PI (10)? The
last two on your list look to be the same thing :)
> - new latency tracer feature: print every function call done by the
> kernel to the console - useful to debug early bootup hangs or other
> nasty bugs.
>
> - plus zillions of bugfixes (and no doubt new regressions).
>
Regressions are going to be the answer to my "when is some of this going
into mainline" question, aren't they :P
> to build a 2.6.16-rc6-rt1 tree, the following patches should be applied:
>
> http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.15.tar.bz2
> http://kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.16-rc6.bz2
> http://redhat.com/~mingo/realtime-preempt/patch-2.6.16-rc6-rt1
>
> Ingo
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
- --
All content of all messages exchanged herein are left in the
Public Domain, unless otherwise explicitly stated.
Creative brains are a valuable, limited resource. They shouldn't be
wasted on re-inventing the wheel when there are so many fascinating
new problems waiting out there.
-- Eric Steven Raymond
We will enslave their women, eat their children and rape their
cattle!
-- Evil alien overlord from Blasto
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQIVAwUBRBhAAAs1xW0HCTEFAQIVPw//Zi/pqBvMlu0kPIlDQ6jfe5LuU1aJ8iaV
g/1K7G0RV+PVkUE6LFgeTwtYPBaCCjELY6aU1zQa/8pPKofOXB7Rd5PYSXqzoVtr
n0Wdpjwkz7sTjY15b6WtfymHgPxukin8JytFzdmITuD+oYOuP5W1zfXgHnYmghpM
QnCuEmvbmpEQmLHrLgAjpjT4h9dwbCGqMm3RWk1mE6vo08hU7P8bX+qtYJ20kOXJ
dYh/ZU0TkFxIoa4GC1eSe+w5zawyIpldHthswwom61MXz8yb5cNfXRwv+zv1TpHW
lvnefxkQLya1cRQME34Pb37PRnylg2TH7DRmPDxOfZ4hTFHoZ6nGWSRBIBe1PQT6
Za+aeSqFuYKI4qevDXrzwKoEb4AqLsVdvhl/+/HB+meKI3pn0ceeAvuRv4dJsBXx
is5eejtoc4lTzNbbOaOMyTOB6TFjdIN0opRN8HLrLkU/JR6aLyeZfaMEEA9Qasfr
9u2Zacphepgmw9gqnVGWhhrliQP8FluE2lt+JluLDMgkbXQHnzjRrDK75c66OB3J
a/QJH/pAtM3xIs/cqmnoOz5Exz6v42QywYoRJ5xxG0pV4e/DWLTn+fByRcZaYYo4
2EaNChymEI8kgzKuuTByWcxzGi02zMgW5Af21QVl7sF6H1iQGQpkKIGAz0we64lK
UW+yDCaQrTU=
=LapY
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2006-03-15 16:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-12 22:02 2.6.16-rc6-rt1 Ingo Molnar
2006-03-12 23:17 ` 2.6.16-rc6-rt1 Michal Piotrowski
2006-03-12 23:36 ` 2.6.16-rc6-rt1 Michal Piotrowski
2006-03-13 6:43 ` 2.6.16-rc6-rt1 Thomas Gleixner
2006-03-13 9:25 ` 2.6.16-rc6-rt1 Ingo Molnar
2006-03-13 13:49 ` 2.6.16-rc6-rt1 Michal Piotrowski
2006-03-13 6:56 ` [PATCH] 2.6.16-rc6-rt1: Fix redefinition and unknown symbol Jan Altenberg
2006-03-13 9:11 ` Ingo Molnar
2006-03-13 13:21 ` 2.6.16-rc6-rt1 Esben Nielsen
2006-03-13 14:29 ` 2.6.16-rc6-rt1 Ingo Molnar
2006-03-13 16:06 ` 2.6.16-rc6-rt1 Esben Nielsen
2006-03-14 0:22 ` 2.6.16-rc6-rt1 Esben Nielsen
2006-03-14 8:12 ` 2.6.16-rc6-rt1 Ingo Molnar
2006-03-14 8:33 ` 2.6.16-rc6-rt1 Thomas Gleixner
2006-03-14 10:02 ` 2.6.16-rc6-rt1 Esben Nielsen
2006-03-14 10:18 ` 2.6.16-rc6-rt1 Ingo Molnar
2006-03-14 22:02 ` 2.6.16-rc6-rt1 Esben Nielsen
2006-03-14 22:11 ` 2.6.16-rc6-rt1 Ingo Molnar
2006-03-14 22:22 ` 2.6.16-rc6-rt1 Thomas Gleixner
2006-03-15 11:21 ` 2.6.16-rc6-rt1 Esben Nielsen
2006-03-14 22:28 ` 2.6.16-rc6-rt1 Esben Nielsen
2006-03-14 10:58 ` 2.6.16-rc6-rt1 Thomas Gleixner
2006-03-14 20:40 ` 2.6.16-rc6-rt1 Esben Nielsen
2006-03-14 22:00 ` 2.6.16-rc6-rt1 Thomas Gleixner
2006-03-14 1:54 ` 2.6.16-rc6-rt1 Steven Rostedt
2006-03-14 7:51 ` 2.6.16-rc6-rt1 Ingo Molnar
2006-03-14 2:22 ` 2.6.16-rc6-rt1 Steven Rostedt
2006-03-14 8:00 ` 2.6.16-rc6-rt1 Ingo Molnar
2006-03-15 16:25 ` John Richard Moser [this message]
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=44184002.4010109@comcast.net \
--to=nigelenki@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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