![]() ![]() If multiple guests use storage on a filesystem or block device managed by the host operating system, the host will likely schedule I/O more efficiently because it is aware of requests from all guests and knows the physical layout of storage, which may not map linearly to the guests' virtual storage. In virtualized environments, it is not advantageous to schedule I/O at both the guest and hypervisor layers. The host/hypervisor will have an overview of the requests of all guests and have a separate strategy for handling I/O. ![]() The noop scheduler can still combine small requests from the guest OS into larger requests before handing the I/O to the hypervisor, however noop follows the idea to spend as few CPU cycles as possible in the guest for I/O scheduling. It allows the host/hypervisor to optimize the I/O requests and prioritize based on it's view on the I/O from one or multiple guests. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |