KarmicKernelFlavours
440
Comment:
|
1923
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
Describe KernelTeam/Specs/KarmicKernelFlavours here. | Many users and some OEMs are requesting the addition of a 32 bit PAE enabled kernel. Their reasons are thus: * Almost all newer laptops can be purchased or upgraded to have more then 3GB of RAM. * Many users prefer 32 bit user space in order to more easily use proprietary applications such as Skype and Flash. * Existing 32 bit users want a 32 bit upgrade option. |
Line 5: | Line 9: |
i386-generic (no substantial change from Jaunty) i386-generic-pae (generic with PAE enabled) |
* i386-generic (no substantial change from Jaunty) Should the minimum supported instruction set be CONFIG_M686=y? VIA C3, Transmeta Crusoe, and Geode LX are the most common non-Intel embedded x86 CPUs. All support the i686 instruction set (MMX, CMOV). Are there toolset issues with i586 and lower? * i386-generic-pae (generic with PAE enabled) * amd64-generic (no substantial change from Jaunty) Is there enough reasons to continue to carry a separate flavour for the server? The process and I/O scheduler can be set at run-time. The biggest compile time option difference is CONFIG_PREEMPT_VOLUNTARY. * lpia-lpia (no substantial change from Jaunty). Need to think about the impact of true Moorestown support v.s. the i386/Atom approach that we've previously adopted for LPIA. Are there upgrade issues? * armel-armv7 - compiling for v7 may force a number of the ARM SOCs to be dropped. Is it still armel ? |
Line 8: | Line 19: |
amd64-generic (no substantial change from Jaunty) amd64-server (no substantial change from Jaunty) |
Note that the i386-server flavour is being dropped. I can think of no good reason to continue to support a 32 bit server. The 32 bit -generic kernel ought to suffice for those headless implementations that have used the -server flavour in the past, such as home gateways. All of the -server unique settings can be made at runtime to a -generic{-pae} kernel, the most important of which are I/O and process scheduler settings. |
Line 11: | Line 21: |
lpia-lpia (no substantial change from Jaunty) armv7 - compiling for v7 may force a number of the ARM SOCs to be dropped. |
A related Blueprint can be found at: https://blueprints.edge.launchpad.net/ubuntu/+spec/use-pae-when-possible |
Many users and some OEMs are requesting the addition of a 32 bit PAE enabled kernel. Their reasons are thus:
- Almost all newer laptops can be purchased or upgraded to have more then 3GB of RAM.
- Many users prefer 32 bit user space in order to more easily use proprietary applications such as Skype and Flash.
- Existing 32 bit users want a 32 bit upgrade option.
The proposed kernel flavours for Karmic are as follows:
- i386-generic (no substantial change from Jaunty)
- Should the minimum supported instruction set be CONFIG_M686=y? VIA C3, Transmeta Crusoe, and Geode LX are the most common non-Intel embedded x86 CPUs. All support the i686 instruction set (MMX, CMOV). Are there toolset issues with i586 and lower?
- i386-generic-pae (generic with PAE enabled)
- amd64-generic (no substantial change from Jaunty)
- Is there enough reasons to continue to carry a separate flavour for the server? The process and I/O scheduler can be set at run-time. The biggest compile time option difference is CONFIG_PREEMPT_VOLUNTARY.
- lpia-lpia (no substantial change from Jaunty).
- Need to think about the impact of true Moorestown support v.s. the i386/Atom approach that we've previously adopted for LPIA. Are there upgrade issues?
- armel-armv7 - compiling for v7 may force a number of the ARM SOCs to be dropped.
- Is it still armel ?
Note that the i386-server flavour is being dropped. I can think of no good reason to continue to support a 32 bit server. The 32 bit -generic kernel ought to suffice for those headless implementations that have used the -server flavour in the past, such as home gateways. All of the -server unique settings can be made at runtime to a -generic{-pae} kernel, the most important of which are I/O and process scheduler settings.
A related Blueprint can be found at: https://blueprints.edge.launchpad.net/ubuntu/+spec/use-pae-when-possible
KernelTeam/Specs/KarmicKernelFlavours (last edited 2009-06-02 09:01:45 by 79-66-138-132)