mirror of
https://github.com/cloud-hypervisor/cloud-hypervisor.git
synced 2024-12-22 05:35:20 +00:00
c297d8d796
Add a 'rate_limit_groups' field to VmConfig that defines a set of named RateLimiterGroups. When the 'rate_limit_group' field of DiskConfig is defined, all virtio-blk queues will be rate-limited by a shared RateLimiterGroup. The lifecycle of all RateLimiterGroups is tied to the Vm. A RateLimiterGroup may exist even if no Disks are configured to use the RateLimiterGroup. Disks may be hot-added or hot-removed from the RateLimiterGroup. When the 'rate_limiter' field of DiskConfig is defined, we construct an anonymous RateLimiterGroup whose lifecycle is tied to the Disk. This is primarily done for api backwards compatability. Importantly, the behavior is not the same! This implementation rate_limits the aggregate bandwidth / iops of an individual disk rather than the bandwidth / iops of an individual queue of a disk. When neither the 'rate_limit_group' or the 'rate_limiter' fields of DiskConfig is defined, the Disk is not rate-limited. Signed-off-by: Thomas Barrett <tbarrett@crusoeenergy.com> |
||
---|---|---|
.. | ||
amd_sev_snp.md | ||
api.md | ||
balloon.md | ||
building.md | ||
COPYING.docs | ||
coverage.md | ||
cpu.md | ||
custom-image.md | ||
debug-port.md | ||
device_model.md | ||
fs.md | ||
fuzzing.md | ||
gdb.md | ||
heap-profiling.md | ||
hotplug.md | ||
intel_sgx.md | ||
intel_tdx.md | ||
io_throttling.md | ||
iommu.md | ||
live_migration.md | ||
logging.md | ||
macvtap-bridge.md | ||
memory.md | ||
mshv.md | ||
performance_metrics.md | ||
profiling.md | ||
releases.md | ||
seccomp.md | ||
snapshot_restore.md | ||
tpm.md | ||
tracing.md | ||
uefi.md | ||
vdpa.md | ||
vfio-user.md | ||
vfio.md | ||
vhost-user-blk-testing.md | ||
vhost-user-net-testing.md | ||
virtiofs-root.md | ||
vsock.md | ||
windows.md |