Determining latest stable release.

Determining latest stable release.

[Robert Barrows]

Does the PREEMPT_RT patch have a method of determining latest stable
release?

I notice that 3.0.35 goes up to rt44 was declared a stable release but
so was rt43
Now 3.2.12 goes up to rt22, and that was updated March 23rd with 3.0.35-rt44.

Is there a reason to think that 3.0.35-rt44 is more stable than 3.2.12-rt22?
The real question is: is there a rule of thumb on how you would choose
a rt patched kernel for a production machine?

Thanks.

-Robb Barrows
--
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

Re: Determining latest stable release.

[Clark Williams]

[-- Attachment #1: Type: text/plain, Size: 806 bytes --]

On Tue, 27 Mar 2012 15:59:31 -0500
Robert Barrows <Robert.Barrows@metriainnovation.com> wrote:

> Does the PREEMPT_RT patch have a method of determining latest stable
> release?
> 
> I notice that 3.0.35 goes up to rt44 was declared a stable release but
> so was rt43
> Now 3.2.12 goes up to rt22, and that was updated March 23rd with 3.0.35-rt44.
> 
> Is there a reason to think that 3.0.35-rt44 is more stable than 3.2.12-rt22?
> The real question is: is there a rule of thumb on how you would choose
> a rt patched kernel for a production machine?
> 
> Thanks.
> 
> -Robb Barrows
> --
>

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.

Clark

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: Determining latest stable release.

[Wolfgang Wallner]

What is the relation between these stable releases and what the OSADL  
calls 'latest stable'? [1]

Regards, Wolfgang


[1]  
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:

> On Tue, 27 Mar 2012 15:59:31 -0500
> Robert Barrows <Robert.Barrows@metriainnovation.com> wrote:
>
>> Does the PREEMPT_RT patch have a method of determining latest stable
>> release?
>>
>> I notice that 3.0.35 goes up to rt44 was declared a stable release but
>> so was rt43
>> Now 3.2.12 goes up to rt22, and that was updated March 23rd with  
>> 3.0.35-rt44.
>>
>> Is there a reason to think that 3.0.35-rt44 is more stable than  
>> 3.2.12-rt22?
>> The real question is: is there a rule of thumb on how you would choose
>> a rt patched kernel for a production machine?
>>
>> Thanks.
>>
>> -Robb Barrows
>> --
>>
>
> 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.
>
> Clark

Re: Determining latest stable release.

[Clark Williams]

[-- Attachment #1: Type: text/plain, Size: 1493 bytes --]

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'? [1]
> 
> Regards, Wolfgang
> 
> 
> [1]  
> 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:
> 
> > On Tue, 27 Mar 2012 15:59:31 -0500
> > Robert Barrows <Robert.Barrows@metriainnovation.com> wrote:
> >
> >> Does the PREEMPT_RT patch have a method of determining latest stable
> >> release?
> >>
> >> I notice that 3.0.35 goes up to rt44 was declared a stable release but
> >> so was rt43
> >> Now 3.2.12 goes up to rt22, and that was updated March 23rd with  
> >> 3.0.35-rt44.
> >>
> >> Is there a reason to think that 3.0.35-rt44 is more stable than  
> >> 3.2.12-rt22?
> >> The real question is: is there a rule of thumb on how you would choose
> >> a rt patched kernel for a production machine?
> >>
> >> Thanks.
> >>
> >> -Robb Barrows
> >> --
> >>
> >
> > 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.
> >
> > Clark


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. 

Clark

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: Determining latest stable release.

[Carsten Emde]

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.