kvm I/O cache 模式
来源:互联网 发布:it盈利模式 编辑:程序博客网 时间:2024/05/21 10:22
KVM针对HOST的cache,可以设置以下几种模式;
- cache mode unspecified
In qemu-kvm versions older than v1.2 (eg SLES11 SP2), not specifying a cache mode meant thatwritethrough would be used as the default. Since that version, the various qemu-kvm guest storage interfaces have been fixed to handlewriteback orwritethrough semantics more correctly, allowing for the default caching mode to be switched towriteback. The guest driver for each ofide, scsi, and virtio have within their power to disable the write back cache, causing the caching mode used to revert towritethrough. The typical guest's storage drivers will maintain the default caching mode aswriteback, however.
- cache = writethrough
This mode causes qemu-kvm to interact with the disk image file or block device with O_DSYNC semantics, where writes are reported as completed only when the data has been committed to the storage device. The host page cache is used in what can be termed a writethrough caching mode. The guest's virtual storage adapter is informed that there is no writeback cache, so the guest would not need to send down flush commands to manage data integrity. The storage behaves as if there is a writethrough cache.
- cache = writeback
This mode causes qemu-kvm to interact with the disk image file or block device with neither O_DSYNC nor O_DIRECT semantics, so the host page cache is used and writes are reported to the guest as completed when placed in the host page cache, and the normal page cache management will handle commitment to the storage device. Additionally, the guest's virtual storage adapter is informed of the writeback cache, so the guest would be expected to send down flush commands as needed to manage data integrity. Analogous to a raid controller with RAM cache.
- cache = none
This mode causes qemu-kvm to interact with the disk image file or block device with O_DIRECT semantics, so the host page cache is bypassed and I/O happens directly between the qemu-kvm userspace buffers and the storage device. Because the actual storage device may report a write as completed when placed in its write queue only, the guest's virtual storage adapter is informed that there is a writeback cache, so the guest would be expected to send down flush commands as needed to manage data integrity. Equivalent to direct access to your hosts' disk, performance wise.
- cache = unsafe
This mode is similar to the cache=writeback mode discussed above. The key aspect of this
unsafe
mode, is that all flush commands from the guests are ignored. Using this mode implies that the user has accepted the trade-off of performance over risk of data loss in the event of a host failure. Useful, for example, during guest install, but not for production workloads.- cache=directsync
This mode causes qemu-kvm to interact with the disk image file or block device with both O_DSYNC and O_DIRECT semantics, where writes are reported as completed only when the data has been committed to the storage device, and when it is also desirable to bypass the host page cache. Like cache=writethrough, it is helpful to guests that do not send flushes when needed. It was the last cache mode added, completing the possible combinations of caching and direct access semantics.
- kvm I/O cache 模式
- Linux I/O及 I/O Cache
- KVM I/O slowness on RHEL 6
- kVM I/O虚拟化分析
- I/O模式概述
- I/O调度模式
- WINSOCKS I/O模式
- I/O模式
- I/O之内核buffer-“buffer cache”
- I/O之内核buffer-“buffer cache”
- qemu-kvm 设备虚拟化----I/O 端口和 I/O 内存
- 套接字I/O模式
- 五种I/O 模式
- 五种I/O 模式
- 五种I/O 模式
- Java I/O装饰模式
- 五种I/O 模式
- 两种I/O模式
- Spring Boot之配置虚拟映射路径
- 安卓手机锁屏收发消息问题
- time相关函数
- linux系统基本操作——存储设备的管理
- 数据库系统之除法运算
- kvm I/O cache 模式
- centos 上传下载
- Unity Shader-遮挡处理
- 初识Spring_05
- impala遇到的坑
- 安卓微信浏览器刷新
- 洛谷P3093 [USACO13DEC]牛奶调度Milk Scheduling(贪心)
- java.lang.NoClassDefFoundError: Lorg/apache/logging/log4j/Logger解决办法
- lua学习笔记——元表(Metatable)