#
af74de27 |
| 07-Feb-2025 |
Ruoqing He <heruoqing@iscas.ac.cn> |
docs: Fix broken link in io_throttling.md
There is a link referencing `rate-limiter` module of `firecracker`, but that module no longer exsits.
Point the link to a commit with the same date in `fir
docs: Fix broken link in io_throttling.md
There is a link referencing `rate-limiter` module of `firecracker`, but that module no longer exsits.
Point the link to a commit with the same date in `firecracker` when this commit was merged to `cloud-hypervisor`.
Format `io_throttling.md` using `mdformat` with GitHub Flavored Markdown (GFM).
Signed-off-by: Ruoqing He <heruoqing@iscas.ac.cn>
show more ...
|
#
c297d8d7 |
| 07-Dec-2023 |
Thomas Barrett <tbarrett@crusoeenergy.com> |
vmm: use RateLimiterGroup for virtio-blk devices
Add a 'rate_limit_groups' field to VmConfig that defines a set of named RateLimiterGroups.
When the 'rate_limit_group' field of DiskConfig is define
vmm: use RateLimiterGroup for virtio-blk devices
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>
show more ...
|
#
a87d1bba |
| 19-Apr-2022 |
Fabiano Fidêncio <fabiano.fidencio@intel.com> |
docs: Fix the name of the I/O operations knobs
The I/O operations knobs are prefixed `ops_` rather than `bw_`, as `bw_` refers to the "bandwidth" knobs.
Signed-off-by: Fabiano Fidêncio <fabiano.fid
docs: Fix the name of the I/O operations knobs
The I/O operations knobs are prefixed `ops_` rather than `bw_`, as `bw_` refers to the "bandwidth" knobs.
Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com>
show more ...
|
#
32ad4982 |
| 25-Mar-2021 |
Bo Chen <chen.bo@intel.com> |
virtio-devices: Add rate limiter for the RX queue of virtio-net
Fixes: #1286
Signed-off-by: Bo Chen <chen.bo@intel.com>
|
#
0c754147 |
| 10-Mar-2021 |
Bo Chen <chen.bo@intel.com> |
docs: Add documentation on I/O throttling
Signed-off-by: Bo Chen <chen.bo@intel.com>
|