Chrome Os
[Target & Application]{
The Chrome OS is designed to work with only specific hardware produced by Google such as Chromebook. It is created for user who spend most of the time on the Web. Hence, only a browser, a media player and a file manager are pre-installed together with the Chrome OS.
}
[Scheduling]{ Chrome Operating System runs the Linux 3.4.6 kernel which utilizes the Completely Fair Scheduler. This is to ensure fairness by allowing processes an equal share of the CPU. To do this, the scheduler keeps track of the amount of time each process has had with the CPU using a virtual runtime. The Completely Fair Scheduler also allows group scheduling. Group scheduling ensures that in situations where tasks spawn other tasks, each single task is ensured their own virtual runtime rather than treating tasks uniformly.
}
[Kernel Structure]{
Chrome OS is designed based on the Monolithic kernel. However, no related information can be found. From the analysis of kernel structure, the authors think that the Monolithic kernel is adopted because Chrome OS is a simple OS that provides only limited services. Hence, the code is small and easier to maintain. In this case, it is worth to use Monolithic kernel for the faster performance.
The Chrome OS uses the Linux Kernel. Historically they stayed on a 2.6.32 Ubuntu-based for the first several releases, but have since then moved on to track the upstream mainline kernel constantly, applying the changes for the features and stability they need on top of it.
}
[Memory Management]{
================================================================================================== ++Address space++
When a Native Client module is loaded into a browser tab it will run in a separate process, distinct from the render process for the tab itself. Chrome creates a fixed-size address space for the new process; 1 GB of memory for an ARM or x86-32 target architecture and 4 GB for an x86-64
The Chrome OS is designed to work with only specific hardware produced by Google such as Chromebook. It is created for user who spend most of the time on the Web. Hence, only a browser, a media player and a file manager are pre-installed together with the Chrome OS.
}
[Scheduling]{ Chrome Operating System runs the Linux 3.4.6 kernel which utilizes the Completely Fair Scheduler. This is to ensure fairness by allowing processes an equal share of the CPU. To do this, the scheduler keeps track of the amount of time each process has had with the CPU using a virtual runtime. The Completely Fair Scheduler also allows group scheduling. Group scheduling ensures that in situations where tasks spawn other tasks, each single task is ensured their own virtual runtime rather than treating tasks uniformly.
}
[Kernel Structure]{
Chrome OS is designed based on the Monolithic kernel. However, no related information can be found. From the analysis of kernel structure, the authors think that the Monolithic kernel is adopted because Chrome OS is a simple OS that provides only limited services. Hence, the code is small and easier to maintain. In this case, it is worth to use Monolithic kernel for the faster performance.
The Chrome OS uses the Linux Kernel. Historically they stayed on a 2.6.32 Ubuntu-based for the first several releases, but have since then moved on to track the upstream mainline kernel constantly, applying the changes for the features and stability they need on top of it.
}
[Memory Management]{
================================================================================================== ++Address space++
When a Native Client module is loaded into a browser tab it will run in a separate process, distinct from the render process for the tab itself. Chrome creates a fixed-size address space for the new process; 1 GB of memory for an ARM or x86-32 target architecture and 4 GB for an x86-64