mirror of
https://github.com/cloud-hypervisor/cloud-hypervisor.git
synced 2024-12-22 05:35:20 +00:00
6956306604
When the rate limit was reached it was possible for the notification to the guest to be lost since the logic to handle the notification was tightly coupled with processing the queue. The notification would eventually be triggered when the rate limit pool was refilled but this could add significant latency. Address this by refactoring the code to separate processing queue and signalling - the processing of the queue is suspended when the rate limit is reached but the signalling will still be attempted if needed (i.e. VIRTIO_F_EVENT_IDX is still considered.) Signed-off-by: wuxinyue <wuxinyue.wxy@antgroup.com> Signed-off-by: Rob Bradford <rbradford@rivosinc.com> |
||
---|---|---|
.. | ||
src | ||
build.rs | ||
Cargo.toml |