COMP 3000 Essay 1 2010 Question 1 - Revision history

Soma: Unprotected "COMP 3000 Essay 1 2010 Question 1"

2010-11-08T15:30:08Z

Unprotected "COMP 3000 Essay 1 2010 Question 1"

← Older revision	Revision as of 15:30, 8 November 2010
(No difference)

Soma: Protected "COMP 3000 Essay 1 2010 Question 1" ([edit=sysop] (indefinite) [move=sysop] (indefinite))

2010-10-15T13:34:16Z

Protected "COMP 3000 Essay 1 2010 Question 1" ([edit=sysop] (indefinite) [move=sysop] (indefinite))

← Older revision	Revision as of 13:34, 15 October 2010
(No difference)

Jslonosky: /* References */

2010-10-15T02:48:19Z

References

← Older revision		Revision as of 02:48, 15 October 2010
Line 70:		Line 70:

	[9]<nowiki>Fisher-Ogden J. 2006. Hardware Support for Efficient Virtualization. University of California, San Diego.		[9]<nowiki>Fisher-Ogden J. 2006. Hardware Support for Efficient Virtualization. University of California, San Diego.

	http://cseweb.ucsd.edu/~jfisherogden/hardwareVirt.pdf</nowiki>		http://cseweb.ucsd.edu/~jfisherogden/hardwareVirt.pdf</nowiki>

	=Misc=		=Misc=
	* every thing is moved to discussion page		* every thing is moved to discussion page

Jslonosky: /* References */

2010-10-15T02:48:09Z

References

← Older revision		Revision as of 02:48, 15 October 2010
Line 68:		Line 68:
	[8]<nowiki> Roch, Benjamin 2004. Microkernel Verses Monolithic Kernel. Vienna University of Technology, Wien, Österreich.		[8]<nowiki> Roch, Benjamin 2004. Microkernel Verses Monolithic Kernel. Vienna University of Technology, Wien, Österreich.
	http://www.vmars.tuwien.ac.at/courses/akti12/journal/04ss/article_04ss_Roch.pdf </nowiki>		http://www.vmars.tuwien.ac.at/courses/akti12/journal/04ss/article_04ss_Roch.pdf </nowiki>


	[9]<nowiki>Fisher-Ogden J. 2006. Hardware Support for Efficient Virtualization. University of California, San Diego.		[9]<nowiki>Fisher-Ogden J. 2006. Hardware Support for Efficient Virtualization. University of California, San Diego.

Jslonosky: /* References */

2010-10-15T02:47:53Z

References

← Older revision		Revision as of 02:47, 15 October 2010
Line 70:		Line 70:


	[9]Fisher-Ogden J. 2006. Hardware Support for Efficient Virtualization. University of California, San Diego. http://cseweb.ucsd.edu/~jfisherogden/hardwareVirt.pdf		[9]<nowiki>Fisher-Ogden J. 2006. Hardware Support for Efficient Virtualization. University of California, San Diego.
			http://cseweb.ucsd.edu/~jfisherogden/hardwareVirt.pdf</nowiki>

	=Misc=		=Misc=
	* every thing is moved to discussion page		* every thing is moved to discussion page

Jslonosky at 02:47, 15 October 2010

2010-10-15T02:47:25Z

← Older revision		Revision as of 02:47, 15 October 2010
Line 4:		Line 4:
	=Answer=		=Answer=

	=Introduction=		==Introduction==
	In Computer Science, the kernel is the component at the center of the majority of operating systems. The kernel is a bridge for applications to access the hardware level. It is responsible for managing the system's resources such as memory, disk storage, task management and networking. We are comparing Exokernels to Microkernels and Virtual Machines by looking at how the kernel goes about such management and its connections. In the Exokernel conceptual model, we can see exokernels become much smaller than microkernels because as this design shows, they are tiny and strive to keep functionality limited to protection and multiplexing of resources. The Virtual Machine Implementation of virtualizing all devices on the system may provide compatibility, but it also adds a layer of complexity within the system. This is less efficient than a real machine as it accesses the hardware indirectly. It can be observed by examining how the exokernel provides low level hardware access and provides custom abstraction to those devices. This is done in order to improve program performance as opposed to a VM's implementation. The exokernel concept has a design that can take the better concepts of microkernels and virtual machines to the extent that exokernels can be seen as a compromise between a virtual machine and a microkernel.		In Computer Science, the kernel is the component at the center of the majority of operating systems. The kernel is a bridge for applications to access the hardware level. It is responsible for managing the system's resources such as memory, disk storage, task management and networking. We are comparing Exokernels to Microkernels and Virtual Machines by looking at how the kernel goes about such management and its connections. In the Exokernel conceptual model, we can see exokernels become much smaller than microkernels because as this design shows, they are tiny and strive to keep functionality limited to protection and multiplexing of resources. The Virtual Machine Implementation of virtualizing all devices on the system may provide compatibility, but it also adds a layer of complexity within the system. This is less efficient than a real machine as it accesses the hardware indirectly. It can be observed by examining how the exokernel provides low level hardware access and provides custom abstraction to those devices. This is done in order to improve program performance as opposed to a VM's implementation. The exokernel concept has a design that can take the better concepts of microkernels and virtual machines to the extent that exokernels can be seen as a compromise between a virtual machine and a microkernel.

	=Microkernels=		==Microkernels==

	The kernel is the most important part of an operating system. An operating system could not function without the kernel.		The kernel is the most important part of an operating system. An operating system could not function without the kernel.
Line 16:		Line 16:
	A microkernel that emerged at the end of the 1980’s to the early 1990’s has the structure that processes as if the File Systems and the Drivers are removed from it, leaving the kernel with process control and input/out control, and interrupts. [8] This new structure makes the system much more modular, and easier to provide solutions. If a driver must be patched or upgraded, the kernel does not need to be recompiled. [7] The old driver can be removed, and during the time the device waits for the system to recognize it, the operating system replaces the driver. This allows for real-time updating, that can be done while the computer is still functional. This can reduce the complete crash of the system. Therefore,if a device fails, the kernel will not crash itself, like a monolithic kernel would. The microkernel can reload the driver of the device that failed and continue functioning. [7]		A microkernel that emerged at the end of the 1980’s to the early 1990’s has the structure that processes as if the File Systems and the Drivers are removed from it, leaving the kernel with process control and input/out control, and interrupts. [8] This new structure makes the system much more modular, and easier to provide solutions. If a driver must be patched or upgraded, the kernel does not need to be recompiled. [7] The old driver can be removed, and during the time the device waits for the system to recognize it, the operating system replaces the driver. This allows for real-time updating, that can be done while the computer is still functional. This can reduce the complete crash of the system. Therefore,if a device fails, the kernel will not crash itself, like a monolithic kernel would. The microkernel can reload the driver of the device that failed and continue functioning. [7]

	=Virtual Machines=		==Virtual Machines==

	A Virtual Machine, or VM, is a software abstraction of a physical machine. This entails virtualization of the physical machines resources in order to share them among OS run in the VM. Virtualizing these resources allow the OS to run as if it were on a full machine when, in reality, it is actually running in a virtualized environment on top of a hostOS. The OS is actually running on the machine, sharing the resources.		A Virtual Machine, or VM, is a software abstraction of a physical machine. This entails virtualization of the physical machines resources in order to share them among OS run in the VM. Virtualizing these resources allow the OS to run as if it were on a full machine when, in reality, it is actually running in a virtualized environment on top of a hostOS. The OS is actually running on the machine, sharing the resources.
Line 34:		Line 34:


	=Exokernels=		==Exokernels==

	Exokernels can be seen as a compromise between a microkernel and a VM. It can also be seen as simply dividing a monolithic kernel up into 2 parts. The management tasks of the kernel remain in the exokernel, these are the raw resource management tasks such as memory management. While the higher level abstractions such as file systems, address spaces, and interprocess communication is done at the application level[1]. These abstractions are usually provided by library OSs which allow applications to handle their own machine resources in ways not possible with the traditional kernel. Which in turn can cause large performance boosts in several areas which will be shown below.		Exokernels can be seen as a compromise between a microkernel and a VM. It can also be seen as simply dividing a monolithic kernel up into 2 parts. The management tasks of the kernel remain in the exokernel, these are the raw resource management tasks such as memory management. While the higher level abstractions such as file systems, address spaces, and interprocess communication is done at the application level[1]. These abstractions are usually provided by library OSs which allow applications to handle their own machine resources in ways not possible with the traditional kernel. Which in turn can cause large performance boosts in several areas which will be shown below.
Line 46:		Line 46:
	Exokernels follow the same design pattern of removing unnecessary code from within the kernel but without the same kernel to user space communication issues that microkernels experience. They also provide through their library OSs a simple yet effective way to emulate several different types of physical resource handling methods similar to virtual machines.		Exokernels follow the same design pattern of removing unnecessary code from within the kernel but without the same kernel to user space communication issues that microkernels experience. They also provide through their library OSs a simple yet effective way to emulate several different types of physical resource handling methods similar to virtual machines.

	=Conclusion=		==Conclusion==

	The kernel is the most important part of the operating system. It manages the processes, and interrupts. It controls the memory and drivers through process management. The microkernel is an improved design of the original kernel. It removed unnecessary processes from the kernel space and moved it into the user space. This made the kernel smaller, more portable and easier to manage. It reduced crashes caused by drivers and other problems. Virtual machines run software that can emulate hardware for an operating system to run on. This allows an operating system to run within an operating system, while sharing the same physical hardware. Though, microkernels and virtual machines have their faults. An Exokernel is seen as a compromise between microkernels and virtual machines. An exokernel contains a condensed kernel similar to a microkernel, and has better control over libraries than a virtual machine has. It can talk to the hardware directly, without the difficulty a microkernel has. Computers are always evolving. The further implementation of exokernels would make a great addition.		The kernel is the most important part of the operating system. It manages the processes, and interrupts. It controls the memory and drivers through process management. The microkernel is an improved design of the original kernel. It removed unnecessary processes from the kernel space and moved it into the user space. This made the kernel smaller, more portable and easier to manage. It reduced crashes caused by drivers and other problems. Virtual machines run software that can emulate hardware for an operating system to run on. This allows an operating system to run within an operating system, while sharing the same physical hardware. Though, microkernels and virtual machines have their faults. An Exokernel is seen as a compromise between microkernels and virtual machines. An exokernel contains a condensed kernel similar to a microkernel, and has better control over libraries than a virtual machine has. It can talk to the hardware directly, without the difficulty a microkernel has. Computers are always evolving. The further implementation of exokernels would make a great addition.

Jslonosky: /* References */

2010-10-15T02:47:04Z

References

@@ Line 50: / Line 50: @@
 The kernel is the most important part of the operating system.  It manages the processes, and interrupts.  It controls the memory and drivers through process management.  The microkernel is an improved design of the original kernel.  It removed unnecessary processes from the kernel space and moved it into the user space.  This made the kernel smaller, more portable and easier to manage.  It reduced crashes caused by drivers and other problems.  Virtual machines run software that can emulate hardware for an operating system to run on.  This allows an operating system to run within an operating system, while sharing the same physical hardware.  Though, microkernels and virtual machines have their faults.  An Exokernel is seen as a compromise between microkernels and virtual machines.  An exokernel contains a condensed kernel similar to a microkernel, and has better control over libraries than a virtual machine has.  It can talk to the hardware directly, without the difficulty a microkernel has.  Computers are always evolving.  The further implementation of exokernels would make a great addition.
-=References=
+==References==
 =Misc=
 * every thing is moved to discussion page

Jslonosky: /* Answer */

2010-10-15T02:41:55Z

Answer

← Older revision		Revision as of 02:41, 15 October 2010
Line 3:		Line 3:

	=Answer=		=Answer=

			=Introduction=
	In Computer Science, the kernel is the component at the center of the majority of operating systems. The kernel is a bridge for applications to access the hardware level. It is responsible for managing the system's resources such as memory, disk storage, task management and networking. We are comparing Exokernels to Microkernels and Virtual Machines by looking at how the kernel goes about such management and its connections. In the Exokernel conceptual model, we can see exokernels become much smaller than microkernels because as this design shows, they are tiny and strive to keep functionality limited to protection and multiplexing of resources. The Virtual Machine Implementation of virtualizing all devices on the system may provide compatibility, but it also adds a layer of complexity within the system. This is less efficient than a real machine as it accesses the hardware indirectly. It can be observed by examining how the exokernel provides low level hardware access and provides custom abstraction to those devices. This is done in order to improve program performance as opposed to a VM's implementation. The exokernel concept has a design that can take the better concepts of microkernels and virtual machines to the extent that exokernels can be seen as a compromise between a virtual machine and a microkernel.		In Computer Science, the kernel is the component at the center of the majority of operating systems. The kernel is a bridge for applications to access the hardware level. It is responsible for managing the system's resources such as memory, disk storage, task management and networking. We are comparing Exokernels to Microkernels and Virtual Machines by looking at how the kernel goes about such management and its connections. In the Exokernel conceptual model, we can see exokernels become much smaller than microkernels because as this design shows, they are tiny and strive to keep functionality limited to protection and multiplexing of resources. The Virtual Machine Implementation of virtualizing all devices on the system may provide compatibility, but it also adds a layer of complexity within the system. This is less efficient than a real machine as it accesses the hardware indirectly. It can be observed by examining how the exokernel provides low level hardware access and provides custom abstraction to those devices. This is done in order to improve program performance as opposed to a VM's implementation. The exokernel concept has a design that can take the better concepts of microkernels and virtual machines to the extent that exokernels can be seen as a compromise between a virtual machine and a microkernel.

			=Microkernels=

	The kernel is the most important part of an operating system. An operating system could not function without the kernel.		The kernel is the most important part of an operating system. An operating system could not function without the kernel.
Line 13:		Line 16:
	A microkernel that emerged at the end of the 1980’s to the early 1990’s has the structure that processes as if the File Systems and the Drivers are removed from it, leaving the kernel with process control and input/out control, and interrupts. [8] This new structure makes the system much more modular, and easier to provide solutions. If a driver must be patched or upgraded, the kernel does not need to be recompiled. [7] The old driver can be removed, and during the time the device waits for the system to recognize it, the operating system replaces the driver. This allows for real-time updating, that can be done while the computer is still functional. This can reduce the complete crash of the system. Therefore,if a device fails, the kernel will not crash itself, like a monolithic kernel would. The microkernel can reload the driver of the device that failed and continue functioning. [7]		A microkernel that emerged at the end of the 1980’s to the early 1990’s has the structure that processes as if the File Systems and the Drivers are removed from it, leaving the kernel with process control and input/out control, and interrupts. [8] This new structure makes the system much more modular, and easier to provide solutions. If a driver must be patched or upgraded, the kernel does not need to be recompiled. [7] The old driver can be removed, and during the time the device waits for the system to recognize it, the operating system replaces the driver. This allows for real-time updating, that can be done while the computer is still functional. This can reduce the complete crash of the system. Therefore,if a device fails, the kernel will not crash itself, like a monolithic kernel would. The microkernel can reload the driver of the device that failed and continue functioning. [7]

			=Virtual Machines=

	A Virtual Machine, or VM, is a software abstraction of a physical machine. This entails virtualization of the physical machines resources in order to share them among OS run in the VM. Virtualizing these resources allow the OS to run as if it were on a full machine when, in reality, it is actually running in a virtualized environment on top of a hostOS. The OS is actually running on the machine, sharing the resources.		A Virtual Machine, or VM, is a software abstraction of a physical machine. This entails virtualization of the physical machines resources in order to share them among OS run in the VM. Virtualizing these resources allow the OS to run as if it were on a full machine when, in reality, it is actually running in a virtualized environment on top of a hostOS. The OS is actually running on the machine, sharing the resources.
Line 30:		Line 34:


			=Exokernels=

	Exokernels can be seen as a compromise between a microkernel and a VM. It can also be seen as simply dividing a monolithic kernel up into 2 parts. The management tasks of the kernel remain in the exokernel, these are the raw resource management tasks such as memory management. While the higher level abstractions such as file systems, address spaces, and interprocess communication is done at the application level[1]. These abstractions are usually provided by library OSs which allow applications to handle their own machine resources in ways not possible with the traditional kernel. Which in turn can cause large performance boosts in several areas which will be shown below.		Exokernels can be seen as a compromise between a microkernel and a VM. It can also be seen as simply dividing a monolithic kernel up into 2 parts. The management tasks of the kernel remain in the exokernel, these are the raw resource management tasks such as memory management. While the higher level abstractions such as file systems, address spaces, and interprocess communication is done at the application level[1]. These abstractions are usually provided by library OSs which allow applications to handle their own machine resources in ways not possible with the traditional kernel. Which in turn can cause large performance boosts in several areas which will be shown below.
Line 41:		Line 46:
	Exokernels follow the same design pattern of removing unnecessary code from within the kernel but without the same kernel to user space communication issues that microkernels experience. They also provide through their library OSs a simple yet effective way to emulate several different types of physical resource handling methods similar to virtual machines.		Exokernels follow the same design pattern of removing unnecessary code from within the kernel but without the same kernel to user space communication issues that microkernels experience. They also provide through their library OSs a simple yet effective way to emulate several different types of physical resource handling methods similar to virtual machines.

			=Conclusion=

			The kernel is the most important part of the operating system. It manages the processes, and interrupts. It controls the memory and drivers through process management. The microkernel is an improved design of the original kernel. It removed unnecessary processes from the kernel space and moved it into the user space. This made the kernel smaller, more portable and easier to manage. It reduced crashes caused by drivers and other problems. Virtual machines run software that can emulate hardware for an operating system to run on. This allows an operating system to run within an operating system, while sharing the same physical hardware. Though, microkernels and virtual machines have their faults. An Exokernel is seen as a compromise between microkernels and virtual machines. An exokernel contains a condensed kernel similar to a microkernel, and has better control over libraries than a virtual machine has. It can talk to the hardware directly, without the difficulty a microkernel has. Computers are always evolving. The further implementation of exokernels would make a great addition.

	~~- Conclusion - Coming soon~~		=References=

	=Misc=		=Misc=
	* every thing is moved to discussion page		* every thing is moved to discussion page

Jslonosky: /* Answer */

2010-10-15T01:43:51Z

Answer

← Older revision		Revision as of 01:43, 15 October 2010
Line 40:		Line 40:

	Exokernels follow the same design pattern of removing unnecessary code from within the kernel but without the same kernel to user space communication issues that microkernels experience. They also provide through their library OSs a simple yet effective way to emulate several different types of physical resource handling methods similar to virtual machines.		Exokernels follow the same design pattern of removing unnecessary code from within the kernel but without the same kernel to user space communication issues that microkernels experience. They also provide through their library OSs a simple yet effective way to emulate several different types of physical resource handling methods similar to virtual machines.


			- Conclusion - Coming soon

	=Misc=		=Misc=
	* every thing is moved to discussion page		* every thing is moved to discussion page

Jslonosky: /* Answer */

2010-10-15T01:43:27Z

Answer