From: David Kastrup <dak@gnu.org>
To: linux-kernel@vger.kernel.org
Cc: linux-rt-users@vger.kernel.org
Subject: Re: [ANNOUNCE] 3.0-rc7-rt0
Date: Wed, 20 Jul 2011 11:02:40 +0200 [thread overview]
Message-ID: <87hb6hpbnz.fsf@fencepost.gnu.org> (raw)
In-Reply-To: alpine.LFD.2.02.1107200153070.2702@ionos
Thomas Gleixner <tglx@linutronix.de> writes:
> The overall patch size has shrunk significantly and the readability
> (except for the missing changelogs in various patches) is at an
> acceptable level.
Well, thanks for all the work. I am actually already using per-irq
threads and priorities on a 3.0-rc kernel (there is some boot option to
enable them), and that helps for audio operation.
It would be really great if realtime can move upstream completely
eventually, and it looks like the current approach is a better match to
the existing kernel, partly due to upstream improvements, partly through
rewritten realtime code.
The ongoing work seems very promising and seems to involve fewer
compromises, boding well not just for the chances of getting merged
upstream, but also of minimizing regressions compared to the
non-realtime kernel.
Thanks!
--
David Kastrup
next prev parent reply other threads:[~2011-07-20 9:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 0:37 [ANNOUNCE] 3.0-rc7-rt0 Thomas Gleixner
2011-07-20 2:48 ` Frank Rowand
2011-07-20 3:22 ` Fernando Lopez-Lezcano
2011-07-20 5:03 ` Paul E. McKenney
2011-07-20 9:02 ` David Kastrup [this message]
2011-07-20 9:48 ` Geunsik Lim
2011-07-20 11:08 ` Armin Steinhoff
2011-07-20 17:02 ` Darren Hart
2011-07-20 18:35 ` [ANNOUNCE] 3.0-rc7-rt0 (hang then panic on dual socket xeon) Darren Hart
2011-07-20 19:10 ` [PATCH] Fix build failure for modular ext3/4 builds Uwe Kleine-König
2011-07-20 19:15 ` [ANNOUNCE] 3.0-rc7-rt0 Noah Watkins
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=87hb6hpbnz.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@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