A final problem with layered implementations is that they tend to be less efficient than other types. For instance, when a user program executes an I/O operation, it executes a system call that is trapped to the I/O layer, which calls the memory-management layer, which in turn calls the CPU-scheduling layer, which is then passed to the hardware. At each layer, the parameters may be modified, data may need to be passed, and so on. Each layer adds overhead to the system call. The net result is a system call that takes longer than does one on a nonlayered system
If you want to change selection, open document below and click on "Move attachment"
pdfs
- owner: miller - (no access) - Abraham Silberschatz_ Peter B Galvin_ Greg Gagne -Operating system concepts-Wiley (2012).pdf, p105
- owner: hughleat - (no access) - Abraham-Silberschatz-Operating-System-Concepts---9th2012.12.pdf, p105
Summary
status | not read | | reprioritisations | |
---|
last reprioritisation on | | | suggested re-reading day | |
---|
started reading on | | | finished reading on | |
---|
Details