From: Ove Karlsen <ove.karlsen@paradoxuncreated.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 3.6.5-rt14
Date: Sat, 03 Nov 2012 20:04:58 +0100 [thread overview]
Message-ID: <50956ADA.6090108@paradoxuncreated.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1211012148170.2756@ionos>
Den 01.11.2012 21:57, skrev Thomas Gleixner:
> Dear RT Folks,
>
> I'm pleased to announce the 3.6.5-rt14 release. 3.6.4-rt12 is an
> intermediate release with a few changes. 3.6.5-rt13 is an update to
> 3.6.5 and 3.6.5-rt14 has a fix for my stupidity to release from the
> wrong tree missing a fix for x86-32.
>
> Changes since 3.6.3-rt11:
>
> * Fix the fallout of preempt_lazy
>
> * Add preempt_lazy support for ARM and POWERPC
>
> * Fix a 32bit compile warning which got introduced with the
> random fixes.
>
> * Fix a missing lock conversion in the decive tree code
>
> The delta patch against 3.6.4-rt11 is can be found here:
>
> http://www.kernel.org/pub/linux/kernel/projects/rt/3.6/incr/patch-3.6.4-rt11-rt12.patch.xz
>
> The RT patch against 3.6.5 can be found here:
>
> http://www.kernel.org/pub/linux/kernel/projects/rt/3.6/patch-3.6.5-rt14.patch.xz
>
> The split quilt queue is available at:
>
> http://www.kernel.org/pub/linux/kernel/projects/rt/3.6/patches-3.6.5-rt14.tar.xz
>
> Enjoy,
>
> tglx
> --
> 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/
>
Heya I see jitter is a focus on the RT patch.
I was wondering, what settings in features.h gives the least jitter? (I
am a real perfectionist)
Also what kind of threadpriorities gives the least jitter, particulary
with a focus on OpenGL? (Should some kernelthreads be reniced, for
instance softirqs etc)
And have you given consideration to the fact that most distros and OS
grow with some levels of bloat, and everyone can`t be an expert, so
maybe one shold consider a (scheduler) queue for "bloat", and one queue
for main app, so that even bloated distros can run with the jitteramount
of a highly specialized distro? (for instance
mainapp,service1,mainapp,service2,mainapp,service3), if bloat is on
queue 2. Or is thins kind of thinking already in batch, or idle?
--
Fred være med deg / Peace Be with You,
Ove Karlsen
http://www.paradoxuncreated.com
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-11-03 20:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 20:57 [ANNOUNCE] 3.6.5-rt14 Thomas Gleixner
2012-11-02 16:58 ` Paul Gortmaker
2012-11-03 19:04 ` Ove Karlsen [this message]
2012-11-06 5:30 ` Valdis.Kletnieks
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=50956ADA.6090108@paradoxuncreated.com \
--to=ove.karlsen@paradoxuncreated.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.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