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:11, 27 June 2012
, 12 years agono edit summary
No edit summary |
|||
Line 13:
You need I/O to communicate, how else do you control the HDD, tell the user what your doing or get input from the user?
== Common
''Note:These are sorted by difficulty''
=== Megalithic ===
Line 23:
{{Rating|1}}
{{main|Monolithic Kernel}}
It keeps to itself most of the time, but its mother is making it play 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 can be unstable if not written correctly, 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
=== Micro ===
{{Rating|2}}
{{main|Microkernel}}
It is very social, and loves to play almost the whole day with user-mode. A Microkernel tries to export all functionality into user-space. It is generally very stable, as if a server or daemon crashes, it can be restarted by the kernel or init. The main thing you want to be fast here is the [[Inter-Process Communication]], as processes will need to be switched between quickly. This isn't the fastest, but probably is best when stability is required. This
=== Hybrid ===
| |||