Talk:COMP 3000 Essay 1 2010 Question 1: Difference between revisions
No edit summary |
mNo edit summary |
||
| Line 13: | Line 13: | ||
-Rovic | -Rovic | ||
Outlining some main features here as I see them. | Outlining some main features here as I see them. | ||
Microkernel | '''Microkernel''' | ||
- Moving kernel functionality into processes contained in user space, e.g. file systems, drivers | - Moving kernel functionality into processes contained in user space, e.g. file systems, drivers | ||
- Keep basic functionality in kernel to handle sharing of resources | - Keep basic functionality in kernel to handle sharing of resources | ||
- Separation allows for manageability and security, corruption in one does not necessarily cause failure in system | - Separation allows for manageability and security, corruption in one does not necessarily cause failure in system | ||
Virtual Machine | '''Virtual Machine''' | ||
- Partitioning or virtualizing resources among OS virtualization running on top of host OS | - Partitioning or virtualizing resources among OS virtualization running on top of host OS | ||
- Virtualized OS believe running on full machine on its own | - Virtualized OS believe running on full machine on its own | ||
Exokernel | '''Exokernel''' | ||
- Microkernel architecture with limited abstractions, ask for resource, get resource not resource abstraction | - Microkernel architecture with limited abstractions, ask for resource, get resource not resource abstraction | ||
- Less functionality provided by kernel, security and handling of resource sharing | - Less functionality provided by kernel, security and handling of resource sharing | ||
| Line 30: | Line 30: | ||
- Keep the basic kernel to handle allocating resources and sharing rather than developing straight to the hardware | - Keep the basic kernel to handle allocating resources and sharing rather than developing straight to the hardware | ||
I found that the exokernel was an even lower-level design than the microkernel, closer to the hardware without abstraction. They have the same architecture with the basic functionality contained in the kernel to manage everyone. As the exokernel "gives" the resource to the application it can use the resource in isolation of other applications (until forced to shared) much like VMs receive their resources, either partitioned or virtualized, and execute as if its running on its own machine. There is this similar notion of partitioning the resources among applications/OS and allowing them to take control of what they have. - | I found that the exokernel was an even lower-level design than the microkernel, closer to the hardware without abstraction. They have the same architecture with the basic functionality contained in the kernel to manage everyone. As the exokernel "gives" the resource to the application it can use the resource in isolation of other applications (until forced to shared) much like VMs receive their resources, either partitioned or virtualized, and execute as if its running on its own machine. There is this similar notion of partitioning the resources among applications/OS and allowing them to take control of what they have. | ||
I'll locate some references later on. --[[User:Slay|Slay]] 15:00, 7 October 2010 (UTC) | |||
Revision as of 15:00, 7 October 2010
Exokernel- Minimalistic abstractions for developers Exokernels can be seen as a good compromise between virtual machines and microkernels in the sense that exokernels can give that low level access to developers similar to direct access through a protected layer and at the same time can contain enough hardware abstraction to allow similar benefit of hiding the hardware resources to application programs. Exokernel – fewest hardware abstractions to developer Microkernel - is the near-minimum amount of software that can provide the mechanisms needed to implement an operating system Virtual machine is a simulation of any or devices requested by an application program Exokenel – I’ve got a sound card Virtual Machine – I’ve got the sound card you’re looking for, perfect virtual match Microkernel – I’ve got sound card that plays Khazikstan sound format only MicroKernel - Very small, very predictable, good for schedualing (QNX is a microkernel - POSIX compatable, benefits of running linux software like modern browsers)
This is some ideas I've got on this question, please contribute below -Rovic
Outlining some main features here as I see them.
Microkernel - Moving kernel functionality into processes contained in user space, e.g. file systems, drivers - Keep basic functionality in kernel to handle sharing of resources - Separation allows for manageability and security, corruption in one does not necessarily cause failure in system
Virtual Machine - Partitioning or virtualizing resources among OS virtualization running on top of host OS - Virtualized OS believe running on full machine on its own
Exokernel - Microkernel architecture with limited abstractions, ask for resource, get resource not resource abstraction - Less functionality provided by kernel, security and handling of resource sharing - Once application receives resource, it can use it as it wishes/in control - Keep the basic kernel to handle allocating resources and sharing rather than developing straight to the hardware
I found that the exokernel was an even lower-level design than the microkernel, closer to the hardware without abstraction. They have the same architecture with the basic functionality contained in the kernel to manage everyone. As the exokernel "gives" the resource to the application it can use the resource in isolation of other applications (until forced to shared) much like VMs receive their resources, either partitioned or virtualized, and execute as if its running on its own machine. There is this similar notion of partitioning the resources among applications/OS and allowing them to take control of what they have.
I'll locate some references later on. --Slay 15:00, 7 October 2010 (UTC)