Hardy

Differences between revisions 4 and 13 (spanning 9 versions)
⇤ ← Revision 4 as of 2007-10-24 07:47:54 →
Size: 3107
Editor: adsl203-157-083
Comment:
← Revision 13 as of 2007-11-06 19:09:00 → ⇥
Size: 6184
Editor: 91
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
 * '''Contributors''':  * '''Contributors''': PeterLJones
Line 13: Line 13:
This specification details the plan to improve hard real time support in Ubuntu Hardy. In particularly for comply with quality that users want by an LTS release. This specification details the plan to improve hard real time support in Ubuntu Hardy. In particular, to comply with quality levels that users want from an LTS release.
Line 25: Line 25:
In order to push Ubuntu in very high demanding business contexts (i.e. industrial automation, financial, robotics and telco) it is necessary to improve realtime kernel flavour support. In order to push Ubuntu in very highly demanding business (e.g. industrial automation, financial, robotics, advanced multimedia and telco) and other contexts, it is necessary to improve real-time kernel flavour support.
Line 29: Line 29:
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. Alex is developing an application ([http://en.wikipedia.org/wiki/SCADA SCADA] type) for a customer and he would be very happy to use Linux and Ubuntu for the deployment.

Beth is a user wanting application stability but with real-time performance capability for running Audio and MIDI applications (such as [http://jackaudio.org/ JACK] and its clients). This could include running a full [http://www.x.org X]/[http://www.gtk.org Gtk] UI stack with [http://www.winehq.com WINE] and/or [http://www.joebutton.co.uk/fst/ FST], with networking to allow for collaborative performances (e.g. [http://ninjam.com NINJAM]). Stability: must be reliable enough for live performance (system hangs look terribly unprofessional). Performance: no dropped MIDI messages (hanging notes suck...), no dropped audio frames (audio glitches suck...).
Line 33: Line 35:
##== Assumptions == == Scope ==

This specification covers the rt linux kernel flavour in Ubuntu.

== Assumptions ==

 * [wiki:KernelTeam/Hardy/KernelVersion Kernel Version]: 2.6.24?
 * [http://lwn.net/Articles/230501/ Scheduler] in stock kernel: CFS
Line 67: Line 76:
##== Outstanding Issues == == Outstanding Issues ==
Line 72: Line 81:
 * How will -rt fare with the introduction of CFS, replacing O(1).

== FAQ ==

'''Q) Did you manage to include all the regular Ubuntu kernel patches in it? If not, is it possible to know what was left out?''' [[BR]]
A) We use _only_ the full Ubuntu Kernel (not vanilla, not custom version or other). The Ubuntu Realtime kernel is the Ubuntu Kernel plus the real-time pre-emption patch. Also the configuration (aka /boot/config*) is the same except for specific real-time options.

'''Q) Where can I find documentation?''' [[BR]]
A) All existing docs are available on http://rt.wiki.kernel.org

'''Q) What are the differences from vanilla Ingo Molnar's patch?''' [[BR]]
A) A simple adaptation to the BenC's kernel git tree isn't the only difference: We work on Ubuntu specific code or drivers (aka linux-ubuntu-modules/linux-restricted-modules) and also remove all code which isn't strictly related to real-time pre-emption support (if any).
Line 74: Line 96:
##Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was ##discussed and note any options that were rejected. *) Team creation? [[BR]]
Collaboration with instant messaging, chat or mailing list? [[BR]]
    I would prefer using a mailing list for team collaboration. [[wiki:DeraldWoods Derald]]
    Ideally a forum; else a mailing list; else a permanent, logged IRC chat room. [[wiki:PeterLJones Peter]]
Line 76: Line 101:
Posix File Capabilties
Backport of the last upstream code
Debug packages		 *) PolicyKit, framework for secure privilege elevation integration, seems which became default in Hardy. Investigate on possible integration. [[BR]]

*) Backport of the last upstream code? [[BR]]
It is necessary define a tool/method to track rt development and thus eventually backport useful bits.

*) Debug packages? [[BR]]
See at https://blueprints.launchpad.net/ubuntu/+spec/daily-kernel-builds

*) RT Test suite? [[BR]]
Thomas Glexiner's rt-tests tools: http://git.kernel.org/?p=linux/kernel/git/tglx/rt-tests.git;a=summary

Need to review: [[BR]]
1. High precision timers don't work on machine which have only PIT as souce clock [http://www.mail-archive.com/linux-rt-users@vger.kernel.org/msg00375.html more info] [[BR]]
2. The realtime kernel could expose you to security issues[[BR]]
3. On some machine esd with realtime kernel freeze GNOME (please kill esd and relaunch it after)[[BR]]
4. Restricted modules could increase latencies (please buy only hardware which have a free driver!) [[BR]]


 * Any suggestions/feedbacks/requests? [wiki:AlessioIgorBogani Alessio] [[BR]][[BR]]

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.

Summary

This specification details the plan to improve hard real time support in Ubuntu Hardy. In particular, to comply with quality levels that users want from an LTS release.

Rationale

In order to push Ubuntu in very highly demanding business (e.g. industrial automation, financial, robotics, advanced multimedia and telco) and other contexts, it is necessary to improve real-time kernel flavour support.

Use Cases

Alex is developing an application ([http://en.wikipedia.org/wiki/SCADA SCADA] type) for a customer and he would be very happy to use Linux and Ubuntu for the deployment.

Beth is a user wanting application stability but with real-time performance capability for running Audio and MIDI applications (such as [http://jackaudio.org/ JACK] and its clients). This could include running a full [http://www.x.org X]/[http://www.gtk.org Gtk] UI stack with [http://www.winehq.com WINE] and/or [http://www.joebutton.co.uk/fst/ FST], with networking to allow for collaborative performances (e.g. [http://ninjam.com NINJAM]). Stability: must be reliable enough for live performance (system hangs look terribly unprofessional). Performance: no dropped MIDI messages (hanging notes suck...), no dropped audio frames (audio glitches suck...).

Scope

This specification covers the rt linux kernel flavour in Ubuntu.

Assumptions

Outstanding Issues

  • How will -rt fare with the introduction of CFS, replacing O(1).

FAQ

Q) Did you manage to include all the regular Ubuntu kernel patches in it? If not, is it possible to know what was left out? BR A) We use _only_ the full Ubuntu Kernel (not vanilla, not custom version or other). The Ubuntu Realtime kernel is the Ubuntu Kernel plus the real-time pre-emption patch. Also the configuration (aka /boot/config*) is the same except for specific real-time options.

Q) Where can I find documentation? BR A) All existing docs are available on http://rt.wiki.kernel.org

Q) What are the differences from vanilla Ingo Molnar's patch? BR A) A simple adaptation to the BenC's kernel git tree isn't the only difference: We work on Ubuntu specific code or drivers (aka linux-ubuntu-modules/linux-restricted-modules) and also remove all code which isn't strictly related to real-time pre-emption support (if any).

BoF agenda and discussion

*) Team creation? BR Collaboration with instant messaging, chat or mailing list? BR

*) PolicyKit, framework for secure privilege elevation integration, seems which became default in Hardy. Investigate on possible integration. BR

*) Backport of the last upstream code? BR It is necessary define a tool/method to track rt development and thus eventually backport useful bits.

*) Debug packages? BR See at https://blueprints.launchpad.net/ubuntu/+spec/daily-kernel-builds

*) RT Test suite? BR Thomas Glexiner's rt-tests tools: http://git.kernel.org/?p=linux/kernel/git/tglx/rt-tests.git;a=summary

Need to review: BR 1. High precision timers don't work on machine which have only PIT as souce clock [http://www.mail-archive.com/linux-rt-users@vger.kernel.org/msg00375.html more info] BR 2. The realtime kernel could expose you to security issuesBR 3. On some machine esd with realtime kernel freeze GNOME (please kill esd and relaunch it after)BR 4. Restricted modules could increase latencies (please buy only hardware which have a free driver!) BR

CategorySpec

RealTime/Hardy (last edited 2008-11-07 15:34:02 by d83-183-69-42)