From: hermann <brummer-@web.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E. McKenney" <paulmck@us.ibm.com>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 3.0-rt7
Date: Fri, 05 Aug 2011 11:12:22 +0200 [thread overview]
Message-ID: <1312535543.2653.5.camel@box> (raw)
In-Reply-To: <1312465990.16729.22.camel@twins>
Am Donnerstag, den 04.08.2011, 15:53 +0200 schrieb Peter Zijlstra:
> Hi,
>
> With Thomas enjoying his well earned holidays, I hereby present you with
> 3.0-rt7.
>
> Goodies included since last time:
>
> - some raw_spinlock patch from Uwe.
> - cpupri rework from Rostedt, something which should greatly benefit
> everybody with smp hardware, the more cpus the more benefit.
> - a possible fix for some posix timer splat reported by Fernando.
> - i386-highmem support because I'd already written the code anyway
> so I thought I might as well make it work.
>
> I'll take patches implementing similar highmem muck on other arches, if
> there's any code to be shared between the arches, do so.
Hi
Many thanks for enable i386-highmem support, the missing highmem was the
biggest issue I've with the latest 3.0-rt patch. Indeed I run into swap
and therewith receive Xruns from jack.
I've just switch back to 2.6.39 some hours before you announce -rt7, now
I'm back on 3.0-rt
lucky I'm
regards
hermann
next prev parent reply other threads:[~2011-08-05 9:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 13:53 [ANNOUNCE] 3.0-rt7 Peter Zijlstra
2011-08-05 9:12 ` hermann [this message]
2011-08-09 13:48 ` [ANNOUNCE] 3.0-rt7 - Error with low latency desktop config Tim Sander
2011-08-09 14:09 ` Uwe Kleine-König
2011-08-09 15:07 ` Tim Sander
2011-08-09 17:33 ` Uwe Kleine-König
2011-08-10 16:33 ` Tim Sander
2011-08-11 10:21 ` Uwe Kleine-König
2011-08-11 11:51 ` Tim Sander
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=1312535543.2653.5.camel@box \
--to=brummer-@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=paulmck@us.ibm.com \
--cc=peterz@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).