Anonymous user
Hybrid Kernel: Difference between revisions
Jump to navigation
Jump to search
m
→Design: removed redundant phrasing
[unchecked revision] | [unchecked revision] |
(New page: {{Template:Kernel designs}} == Design == A hybrid kernel is, as its name indicates, a hybrid between a Monolithic kernel and a Microkernel. Unlike a microkernel where everything ta...) |
m (→Design: removed redundant phrasing) |
||
Line 3:
A hybrid kernel is, as its name indicates, a hybrid between a [[Monolithic kernel]] and a [[Microkernel]]. Unlike a microkernel where everything takes place in user level servers and drivers, the designers of a hybrid kernel may decide to keep several components inside kernel and some outside. There are many motivations for doing so, such as performance, simplicity, and vendor lock-in (you cannot change components with custom components). Most hybrid kernels start as monolithic kernels and begin moving components into user land, primarily as security to support 3rd-party components and drivers which may be malicious or buggy.
An example of a hybrid kernel design may keep the VFS and bus controllers inside the kernel, but have the file system drivers and storage drivers as user mode programs. The advantage of this
== Examples ==
|