User:Lionel/What kind of kernel should I make?: Difference between revisions
Jump to navigation
Jump to search
User:Lionel/What kind of kernel should I make? (view source)
Revision as of 20:20, 24 June 2012
, 12 years agoAdded Monolithic and Megalithic
No edit summary |
(Added Monolithic and Megalithic) |
||
Line 8:
{{main|Interrupts}}
This is a must, because ''any'' kernel needs to handle requests and notifications for the hardware. If the CPU doesn't support some type of signaling system, replace all instances of "interrupt" with "polling".
== Common Kernel Archetypes ==
===
{{main|Megalithic Kernel}}
Difficulty:[[File:Difficulty_1.png]]
----
It only keeps to itself, not sharing anything with user-mode. A Megalithic kernel is probably the easiest because everything is in the kernel binary, which means that there is no task switching. This is probably the kind of kernel you should make if you are developing on a embedded system.
=== Monolithic ===
{{main|Monolithic Kernel}}
Difficulty:[[File:Difficulty_1.png]]
----
It keeps to itself most of the time, but its mother is making it share with user-mode. A Monolithic kernel is basically a big unchanging binary, and if there is any change, the kernel needs to be replaced again. This design is fast, but not stable, as any bug can break the kernel easily. It would work well on a embedded system, but modern Monolithic Kernels, such as Linux, run on PC's as well. This is the second easiest, and is the one most people start out on, as components can be moved to create different archetypes.
| |||