User:Lionel/What kind of kernel should I make?: Difference between revisions

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. There is also no user mode. This is probably the kind of kernel you should make if you are developing on a embedded system.

It keepsSimilar to itselfa mostmegalithic ofkernel; the time, but its mother is making it play with user-mode. Aa Monolithic kernel is basically a big unchanging binary, and if there is any change, the kernel needs to be replaced again. It however has a user space. 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 changed to create different types. Linux is a prime example of this, but most kernels will fall into this category.

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/watchdog. 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 type of kernel is recommended for servers.