Hardy

Differences between revisions 1 and 23 (spanning 22 versions)
⇤ ← Revision 1 as of 2007-10-17 12:58:36 →
Size: 2735
Editor: adsl203-157-083
Comment:
← Revision 23 as of 2007-12-13 11:01:53 → ⇥
Size: 7987
Editor: adsl203-157-083
Comment: Ml creation requested. In the meanwhile we can use kernel-team ml.
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
 * '''Contributors''':  * '''Contributors''': [wiki:PeterLJones PeterLJones], [wiki:DeraldWoods DeraldWoods], [wiki:miguel Miguel]
Line 13: Line 13:
This should provide an overview of the issue/functionality/change proposed here. Focus here on what will actually be DONE, summarising that so that other people don't have to read the whole spec. 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 15: Line 15:
== Release Note ==

This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)

It is mandatory.		 ##== Release Note ==
##
##This section should include a paragraph describing the end-user impact of this change. It is meant to be included
##in the release notes of the first release in which it is implemented. (Not all of these will actually be included
##in the release notes, at the release manager's discretion; but writing them is a useful exercise.)
##
##It is mandatory.
Line 23: Line 25:
This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified. 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 27: Line 29:
== Assumptions == '''1. Deterministic (Hard-Realtime)''' [Industrial Control, Robotics, Automation, DAQ, etc.][[BR]]
Line 29: Line 31:
== Design ==     * 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.
Line 31: Line 33:
You can have subsections that better describe specific parts of the issue.     * John is using the Ubuntu distribution, with the '''linux-rt''' kernel, as the RTOS, for a GANTRY type widget assembly application. The system has digital I/O, servo motors, and GPIB instrumentation.
Line 33: Line 35:
== Implementation == '''2. Non-Deterministic (Low-Latency)''' [Data Sampling, Analysis Tools, Realtime Monitoring, etc.][[BR]]
Line 35: Line 37:
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:     * 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 37: Line 39:
=== UI Changes === ##Other use cases?
Line 39: Line 41:
Should cover changes required to the UI, or specific UI that is required to implement this == Scope ==
Line 41: Line 43:
=== Code Changes === This specification covers the rt linux kernel flavour in Ubuntu.
Line 43: Line 45:
Code changes should include an overview of what needs to change, and in some cases even the specific details. ### == Assumptions ==
Line 45: Line 47:
=== Migration === ## * [wiki:KernelTeam/Hardy/KernelVersion Kernel Version]: 2.6.24?
## * [http://lwn.net/Articles/230501/ Scheduler] in stock kernel: CFS
Line 47: Line 50:
Include:
 * data migration, if any
 * redirects from old URLs to new ones, if any
 * how users will be pointed to the new way of doing things, if necessary.		 ##== Design ==
##
##You can have subsections that better describe specific parts of the issue.
Line 52: Line 54:
== Test/Demo Plan == ##== Implementation ==
##
##This section should describe a plan of action (the "how") to implement the changes discussed. Could include
##subsections like:
Line 54: Line 59:
It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during CD testing, and to show off after release. ##=== UI Changes ===
##
##Should cover changes required to the UI, or specific UI that is required to implement this
Line 56: Line 63:
This need not be added or completed until the specification is nearing beta. ##=== Code Changes ===
##
##Code changes should include an overview of what needs to change, and in some cases even the specific details.
Line 58: Line 67:
== Outstanding Issues == ##=== Migration ===
##
##Include:
## * data migration, if any
## * redirects from old URLs to new ones, if any
## * how users will be pointed to the new way of doing things, if necessary.
Line 60: Line 74:
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved. ##== Test/Demo Plan ==

##It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a
##short plan that anybody can follow that demonstrates the feature is working. This can then be used during CD
##testing, and to show off after release.
##
##This need not be added or completed until the specification is nearing beta.

### == Outstanding Issues ==
##
##This should highlight any issues that should be addressed in further specifications, and not problems with the
##specification itself; since any specification with problems cannot be approved.

## * 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).

'''Q) What features will be included in Ubuntu rt kernel flavour?''' [[BR]]
A) CPU shielding, priority inheritance, sleeping spinlocks, interrupt threads and high-resolution timers and CFS optimizations.

'''Q) How to get the source code? Is there a Git repository?''' [[BR]]
A) (I belive there is no Git repository. The best way is, I guess, get the Ubuntu kernel from the Git repository at http://kernel.ubuntu.com and then apply the patch from Ingo Molnar. Is there a patch package? Alessio, could you please elaborate on this?)
Line 64: Line 108:
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. *) 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.

 * Packaging the '''rt-tests''' utilities. [[http://rt.wiki.kernel.org/index.php/Cyclictest cyclictest/signaltest]] [[http://rt.wiki.kernel.org/index.php/Preemption_Test preemption test]] [[http://devresources.linux-foundation.org/craiger/hackbench/ hackbench]]

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

There are some other test applications on http://rt.wiki.kernel.org that could also be integrated in a future test suite. And, of course, this test suite could be executed daily, integrated in the daily-kernel-builds referred above. [[wiki:miguel Miguel]]

In this way you testing realtime performance of the buildd server (the Ubuntu server that compile kernel). Testing is a very useful things but it is necessary find an other way for do it. [[wiki:AlessioIgorBogani Alessio]]

*) RT documentation? [[BR]]
I believe that it would be necessary to have some documentation package, at least for application developers. As a starting point, the documentation in the http://rt.wiki.kernel.org could be used but I think that something for newcomers should also be written (in cooperation with the http://rt.wiki.kernel.org maintainers, of course).

Good suggestion! [[wiki:AlessioIgorBogani Alessio]]

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

1. Deterministic (Hard-Realtime) [Industrial Control, Robotics, Automation, DAQ, etc.]BR

  • 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.

  • John is using the Ubuntu distribution, with the linux-rt kernel, as the RTOS, for a GANTRY type widget assembly application. The system has digital I/O, servo motors, and GPIB instrumentation.

2. Non-Deterministic (Low-Latency) [Data Sampling, Analysis Tools, Realtime Monitoring, etc.]BR

  • 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.

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).

Q) What features will be included in Ubuntu rt kernel flavour? BR A) CPU shielding, priority inheritance, sleeping spinlocks, interrupt threads and high-resolution timers and CFS optimizations.

Q) How to get the source code? Is there a Git repository? BR A) (I belive there is no Git repository. The best way is, I guess, get the Ubuntu kernel from the Git repository at http://kernel.ubuntu.com and then apply the patch from Ingo Molnar. Is there a patch package? Alessio, could you please elaborate on this?)

BoF agenda and discussion

*) 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

There are some other test applications on http://rt.wiki.kernel.org that could also be integrated in a future test suite. And, of course, this test suite could be executed daily, integrated in the daily-kernel-builds referred above. wiki:miguel Miguel

In this way you testing realtime performance of the buildd server (the Ubuntu server that compile kernel). Testing is a very useful things but it is necessary find an other way for do it. wiki:AlessioIgorBogani Alessio

*) RT documentation? BR I believe that it would be necessary to have some documentation package, at least for application developers. As a starting point, the documentation in the http://rt.wiki.kernel.org could be used but I think that something for newcomers should also be written (in cooperation with the http://rt.wiki.kernel.org maintainers, of course).

Good suggestion! wiki:AlessioIgorBogani Alessio

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)