From: Carsten Emde <C.Emde@osadl.org>
To: Clark Williams <williams@redhat.com>
Cc: Wolfgang Wallner <wolfgang-wallner@gmx.at>,
linux-rt-users@vger.kernel.org
Subject: Re: Determining latest stable release.
Date: Thu, 29 Mar 2012 00:08:31 +0200 [thread overview]
Message-ID: <4F738BDF.8080904@osadl.org> (raw)
In-Reply-To: <20120328153450.52c62ab8@redhat.com>
On 03/28/2012 10:34 PM, Clark Williams wrote:
> On Wed, 28 Mar 2012 22:27:19 +0200
> "Wolfgang Wallner"<wolfgang-wallner@gmx.at> wrote:
>> What is the relation between these stable releases and what the OSADL
>> calls 'latest stable'?
>> [..]
>> https://www.osadl.org/Latest-Stable-Realtime.latest-stable-realtime-linux.0.html
>> On Wed, 28 Mar 2012 21:00:22 +0200, Clark Williams<williams@redhat.com>
>> wrote:
>> [..]
>>> The stuff that Steven releases is the stable series, while Thomas
>>> does the devel releases. So if you're not looking for the latest and
>>> greatest, I'd stick to what Steven releases.
> I think we'll have to ask Carsten about his stable release criteria. It
> may be that he's being more conservative than us and staying on a 2.6
> kernel.
Yes, indeed. We made the (probably naive) promise to not label a kernel
version "Latest Stable", unless there are no known bugs or regressions.
This means that all our development systems in the QA Farm must be
running this kernel for at least a month under all appropriate load
scenarios without any problem. Please note that some of the load
conditions have been introduced only recently, so it may be harder than
ever for a kernel to pass these tests. But we need these benchmarks in
order to reliably discover performance regressions. In addition, with
the increasing use of Linux in safety-critical systems we need to
provide a stable software basis on top of which additional tests and
procedures can be built.
Many of the pending problems of the RT versions of the 3.0 and the 3.2
kernel have been solved recently, and we now are very close to label one
of the 3.x kernels (probably 3.2) "Latest stable". The most important
problem that really needs to be solved before we even can thing to go
"Latest Stable" are crashes of unknown origin during heavy file I/O.
Only relatively slow and mostly single-core systems are affected. Since
the systems simply stop without any output, our progress with this issue
is very slow.
Except this and another regression that may not be important for the
majority of RT users, the 3.x RT kernel is pretty stable and has
impressive real-time capabilities. Such systems, if thoroughly tested,
certainly may be used in a productive environment. However, the extra
guarantee and confidence levels of an OSADL "Latest Stable" kernel
unfortunately are not yet available.
Hope this helps.
-Carsten.
prev parent reply other threads:[~2012-03-28 22:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOHJ0jTVxzgfBK=GSEr14YrpFZEqFE_qDqftaUgGWDgm344NNg@mail.gmail.com>
2012-03-27 20:59 ` Determining latest stable release Robert Barrows
2012-03-28 19:00 ` Clark Williams
2012-03-28 20:27 ` Wolfgang Wallner
2012-03-28 20:34 ` Clark Williams
2012-03-28 22:08 ` Carsten Emde [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=4F738BDF.8080904@osadl.org \
--to=c.emde@osadl.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@redhat.com \
--cc=wolfgang-wallner@gmx.at \
/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.