RealTime
Size: 1612
Comment:
|
Size: 7201
Comment: Lowatency Lucid removed
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
##(see the SpecSpec for an explanation) | == Realtime == |
Line 3: | Line 3: |
''Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.'' | '''Basic introduction is available at:'''<<BR>> [[https://help.ubuntu.com/community/UbuntuStudio/RealTimeKernel]] <<BR>><<BR>> For a more in-depth look at kernels, please see: [[https://wiki.ubuntu.com/Kernel/Dev]] <<BR>><<BR>> '''News:''' <<BR>> The -preempt and -rt kernels are no longer being developed due to lack of support. Focus has instead turned to the -lowlatency and -realtime kernels, particularly for the the release of Ubuntu 11.04 Natty Narwhal. The long-term goal is to have -lowlatency in the official Ubuntu repositories, while maintaining -realtime in a dedicated PPA.<<BR>><<BR>> As of this writing, there are no alternative kernels (including -realtime and -lowlatency) available for Maverick Meerkat in either the official repositories or any Ubuntu Studio recommended repositories (such as that maintained by [[LaunchpadHome:abogani|Alessio Igor Bogani]]). It is recommended that you use the default -generic kernel with Maverick. <<BR>><<BR>>If you wish to see work continued on -preempt or -rt, you are encouraged to volunteer. To do so, join the Ubuntu Studio Developers e-mail list (see [[http://ubuntustudio.org/|Ubuntu Studio]]). |
Line 5: | Line 13: |
## * '''Launchpad entry''': https://launchpad.net/distros/ubuntu/+spec/realtime * '''Created''': [[Date(2007-01-09T17:28:06Z)]] by AlessioIgorBogani * '''Contributors''': AlessioIgorBogani * '''Packages affected''': linux-source-2.6.20 |
'''Make-up of the team and roles officially assigned:''' ||<-7 #cccccc :> '''Kernel Responsibility Matrix''' || ||<#eeeeee> '''Kernels''' ||<#eeeeee> '''Code & Packaging''' ||<#eeeeee> '''Upstream Relations''' ||<#eeeeee> '''Bug Triage''' ||<#eeeeee> '''Kernel/DKMS External Driver Upload''' ||<#eeeeee> '''Testing''' ||<#eeeeee> '''Video Driver Testing''' || ||<#eeeeee> '''Lucid -realtime i386''' ||<#FFFFCC> none ||<#FFFFCC> none ||<#FFFFCC> none ||<#FFFFCC> none ||<#CCFFCC> Jeremy Jongepier/Asmo Koskinen/Erik Rasmussen/Brian David ||<#CCFFCC> Brian David(fglrx)/Jeremy Jongepier/Asmo Koskinen (nvidia) (nvidia) || ||<#eeeeee> '''Lucid -realtime amd64''' ||<#FFFFCC> none ||<#CCFFCC> Tim Cook ||<#FFFFCC> none ||<#FFFFCC> none ||<#CCFFCC> Laurent Bellegarde/Jeremy Jongepier/Asmo Koskinen ||<#CCFFCC> holstein(nvidia) / Laurent Bellegarde(fglrx)/Jeremy Jongepier (nvidia)/Asmo Koskinen (nvidia) || ||<#eeeeee> '''Natty -lowlatency i386''' ||<#CCFFCC> Luke Yelavich / Scott Lavender / Ronan Jouchet ||<#CCFFCC> Scott Lavender ||<#CCFFCC> Scott Lavender / Ronan Jouchet ||<#CCFFCC> Luke Yelavich ||<#CCFFCC> Scott Lavender / Ronan Jouchet/Asmo Koskinen/Brian David ||<#CCFFCC> Ronan Jouchet (fglrx), Luke Yelavich (NVIDIA)/Asmo Koskinen (nvidia)/Brian David (fglrx)/ ailo(nvidia) || ||<#eeeeee> '''Natty -lowlatency amd64''' ||<#CCFFCC> Luke Yelavich / Janne Jokitalo ||<#CCFFCC> Janne Jokitalo ||<#CCFFCC> Janne Jokitalo ||<#CCFFCC> Luke Yelavich ||<#CCFFCC> Janne Jokitalo/Asmo Koskinen ||<#CCFFCC> Luke Yelavich (NVIDIA)/ Janne Jokitalo (NVIDIA)/Asmo Koskinen (nvidia)/ ailo(nvidia) || ||<#eeeeee> '''Natty -realtime i386''' ||<#CCFFCC> Alessio Igor Bogani ||<#CCFFCC> Alessio Igor Bogani ||<#CCFFCC> Alessio Igor Bogani ||<#FFFFCC> none ||<#CCFFCC> Jeremy Jongepier/Asmo Koskinen/Erik Rasmussen/Brian David ||<#CCFFCC> Jeremy Jongepier (nvidia)/Asmo Koskinen (nvidia)/Brian David (fglrx)/ ailo(nvidia) || ||<#eeeeee> '''Natty -realtime amd64''' ||<#CCFFCC> Alessio Igor Bogani ||<#CCFFCC> Alessio Igor Bogani ||<#CCFFCC> Alessio Igor Bogani ||<#FFFFCC> none ||<#CCFFCC> Tim Cook/Jeremy Jongepier/Asmo Koskinen ||<#CCFFCC> holstein(nvidia)/Jeremy Jongepier (nvidia)/Asmo Koskinen (nvidia)/ ailo(nvidia)|| |
Line 10: | Line 23: |
== Summary == | '''Work in progress:''' <<BR>> Nvidia on -realtime kernel at Alessio's PPA: testers? <<BR>> |
Line 12: | Line 26: |
This specification details the plan to add hard real time support in Ubuntu. | |
Line 14: | Line 27: |
== Rationale == | '''Known issues:''' <<BR>> Missing a decent FAQ section <<BR>> Firewire audio devices: again volunteers? -- <<BR>> --[[LaunchpadHome:autostatic]] (Jeremy Jongepier): I'm willing to volunteer, I'm using several FireWire soundcards on a daily basis. <<BR>> --[[LaunchpadHome:beejunk]] (Brian David): I also use firewire devices and can help here. As usual, mostly with testing.<<BR>> |
Line 16: | Line 33: |
In some contexts (i.e. industrial automation, robotics and telco) the low-latency support is insufficient. In order to push Ubuntu in these contexts is necessary the support for high resolution timers and the full preemption in the Linux kernel. These features have been implemented by Thomas Gleixner and Ingo Molnar (http://people.redhat.com/mingo/realtime-preempt/). | |
Line 18: | Line 34: |
We want also a valid FLOSS alternative to SLERT (http://www.novell.com/products/realtime/). | '''FAQ:''' <<BR>> Q: What is the difference between an -rt kernel and a -realtime kernel? |
Line 20: | Line 37: |
== Use cases == | A: From a technical point of view, -rt and -realtime are the same kernel. They are both based on the PREEMPT_RT patchset, although the version may be different. The main difference is that the -rt kernel should be based on the Ubuntu source tree (and therefore can use the same features, patches, enabled hardware, security fixes and so on) and should offer the same services that the Ubuntu default -generic kernel offers. For example, it should be compatible with closed video drivers (nvidia and fglrx), any external DKMS drivers, and have available backport packages. The goal of an -rt kernel is to obtain a real time variant of the Ubuntu kernel that is aligned with the -generic kernel. <<BR>><<BR>> On the other hand, the -realtime kernel is a PREEMPT_RT patched kernel based on the vanilla source tree (not the Ubuntu source). This kernel will be missing Ubuntu specific code, patches or security fixes and it isn't guaranteed to be compatible with any external software (low level utilities, DKMS drivers and so on). It does not use the same Linux kernel version as the -generic kernel, and so these two kernels are not aligned. It is a working, upstream real-time kernel that is being used on Ubuntu. No more no less. |
Line 22: | Line 41: |
Alex is developing an application software (SCADA type) for a customer and he would be very happy to use Linux and Ubuntu for the deployment. | {{{#!wiki comment |
Line 24: | Line 43: |
== Scope == | -lowlatency == -generic + more aggressive low latency kernel configuration It can offers all things that Ubuntu offer with -generic so -backport modules, video closed drivers and so on. It is very solid and oriented to "soft" users. Trade-off between low latency and power consumption. |
Line 26: | Line 48: |
This specification cover the linux kernel in Ubuntu. | In less words: if you need of closed video drivers, external DKMS kernel modules, linux-backports-* you should probably start to use -lowlatency (when it will be available through Ubuntu repos). Instead if you really need of an real-time system you should avoid all above or trying to make those working alone. |
Line 28: | Line 54: |
== Design == | |
Line 30: | Line 55: |
== Implementation == | To put it simply: -lowlatency all the way! It delivers impressive results for maintenance requirements way lower than -realtime (or -rt even more), meaning less work for maintainers and new kernel candy for users. |
Line 32: | Line 60: |
We hope to add a linux-image-realtime package in universe repositary (the same place of the linux-image-lowlatency package). | Life is a trade-off: someone want a very hard real-time system without adopt other hardware architectures than pc (MCU, FPGA/ASIC, and so on), others want use normal and cheap pc, others want use also accelerated drivers also, others want a real-system which take care of they laptop's batteries too. And at the end we have limited resources(*) for give an answer on these needs (we are all volunteers). |
Line 34: | Line 68: |
=== Code === | }}} |
Line 36: | Line 70: |
=== Data preservation and migration === | |
Line 38: | Line 71: |
== Unresolved issues == | === Ancient stuff === These wiki pages covers hard real time support in Ubuntu. |
Line 40: | Line 74: |
== BoF agenda and discussion == | [[RealTime/Feisty|RealTime Feisty]] <<BR>> [[RealTime/Gutsy|RealTime Gutsy]] <<BR>> [[RealTime/Hardy|RealTime Hardy]] <<BR>> [[RealTime/Intrepid|RealTime Intrepid]] <<BR>> [[RealTime/Jaunty|RealTime Jaunty]] <<BR>> [[RealTime/Karmic|RealTime Karmic]] <<BR>> [[RealTime/Lucid|RealTime Lucid]] |
Line 42: | Line 82: |
---- CategorySpec CategorySpec |
The RT kernel is still around! If you can help by describing it's current state, please do so. In the mean time see the official [[http://rt.wiki.kernel.org|rt.wiki.kernel.org]] and the [[http://ubuntustudio.org/|Ubuntu Studio]] team for more information. |
Realtime
Basic introduction is available at:
https://help.ubuntu.com/community/UbuntuStudio/RealTimeKernel
For a more in-depth look at kernels, please see: https://wiki.ubuntu.com/Kernel/Dev
News:
The -preempt and -rt kernels are no longer being developed due to lack of support. Focus has instead turned to the -lowlatency and -realtime kernels, particularly for the the release of Ubuntu 11.04 Natty Narwhal. The long-term goal is to have -lowlatency in the official Ubuntu repositories, while maintaining -realtime in a dedicated PPA.
As of this writing, there are no alternative kernels (including -realtime and -lowlatency) available for Maverick Meerkat in either the official repositories or any Ubuntu Studio recommended repositories (such as that maintained by Alessio Igor Bogani). It is recommended that you use the default -generic kernel with Maverick.
If you wish to see work continued on -preempt or -rt, you are encouraged to volunteer. To do so, join the Ubuntu Studio Developers e-mail list (see Ubuntu Studio).
Make-up of the team and roles officially assigned:
Kernel Responsibility Matrix |
||||||
Kernels |
Code & Packaging |
Upstream Relations |
Bug Triage |
Kernel/DKMS External Driver Upload |
Testing |
Video Driver Testing |
Lucid -realtime i386 |
none |
none |
none |
none |
Jeremy Jongepier/Asmo Koskinen/Erik Rasmussen/Brian David |
Brian David(fglrx)/Jeremy Jongepier/Asmo Koskinen (nvidia) (nvidia) |
Lucid -realtime amd64 |
none |
Tim Cook |
none |
none |
Laurent Bellegarde/Jeremy Jongepier/Asmo Koskinen |
holstein(nvidia) / Laurent Bellegarde(fglrx)/Jeremy Jongepier (nvidia)/Asmo Koskinen (nvidia) |
Natty -lowlatency i386 |
Luke Yelavich / Scott Lavender / Ronan Jouchet |
Scott Lavender |
Scott Lavender / Ronan Jouchet |
Luke Yelavich |
Scott Lavender / Ronan Jouchet/Asmo Koskinen/Brian David |
Ronan Jouchet (fglrx), Luke Yelavich (NVIDIA)/Asmo Koskinen (nvidia)/Brian David (fglrx)/ ailo(nvidia) |
Natty -lowlatency amd64 |
Luke Yelavich / Janne Jokitalo |
Janne Jokitalo |
Janne Jokitalo |
Luke Yelavich |
Janne Jokitalo/Asmo Koskinen |
Luke Yelavich (NVIDIA)/ Janne Jokitalo (NVIDIA)/Asmo Koskinen (nvidia)/ ailo(nvidia) |
Natty -realtime i386 |
Alessio Igor Bogani |
Alessio Igor Bogani |
Alessio Igor Bogani |
none |
Jeremy Jongepier/Asmo Koskinen/Erik Rasmussen/Brian David |
Jeremy Jongepier (nvidia)/Asmo Koskinen (nvidia)/Brian David (fglrx)/ ailo(nvidia) |
Natty -realtime amd64 |
Alessio Igor Bogani |
Alessio Igor Bogani |
Alessio Igor Bogani |
none |
Tim Cook/Jeremy Jongepier/Asmo Koskinen |
holstein(nvidia)/Jeremy Jongepier (nvidia)/Asmo Koskinen (nvidia)/ ailo(nvidia) |
Work in progress:
Nvidia on -realtime kernel at Alessio's PPA: testers?
Known issues:
Missing a decent FAQ section
Firewire audio devices: again volunteers? --
--autostatic (Jeremy Jongepier): I'm willing to volunteer, I'm using several FireWire soundcards on a daily basis.
--beejunk (Brian David): I also use firewire devices and can help here. As usual, mostly with testing.
FAQ:
Q: What is the difference between an -rt kernel and a -realtime kernel?
A: From a technical point of view, -rt and -realtime are the same kernel. They are both based on the PREEMPT_RT patchset, although the version may be different. The main difference is that the -rt kernel should be based on the Ubuntu source tree (and therefore can use the same features, patches, enabled hardware, security fixes and so on) and should offer the same services that the Ubuntu default -generic kernel offers. For example, it should be compatible with closed video drivers (nvidia and fglrx), any external DKMS drivers, and have available backport packages. The goal of an -rt kernel is to obtain a real time variant of the Ubuntu kernel that is aligned with the -generic kernel.
On the other hand, the -realtime kernel is a PREEMPT_RT patched kernel based on the vanilla source tree (not the Ubuntu source). This kernel will be missing Ubuntu specific code, patches or security fixes and it isn't guaranteed to be compatible with any external software (low level utilities, DKMS drivers and so on). It does not use the same Linux kernel version as the -generic kernel, and so these two kernels are not aligned. It is a working, upstream real-time kernel that is being used on Ubuntu. No more no less.
Ancient stuff
These wiki pages covers hard real time support in Ubuntu.
RealTime Feisty
RealTime Gutsy
RealTime Hardy
RealTime Intrepid
RealTime Jaunty
RealTime Karmic
RealTime Lucid
The RT kernel is still around! If you can help by describing it's current state, please do so. In the mean time see the official rt.wiki.kernel.org and the Ubuntu Studio team for more information.
RealTime (last edited 2011-02-23 10:51:46 by cache1)