-
Notifications
You must be signed in to change notification settings - Fork 2k
[block] simplify unsafe flush behavior #2702
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[block] simplify unsafe flush behavior #2702
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have some measurement for the improvement in performance? I expect this change to speed things up as there would normally be no flush requests to process, but I was wondering if we have some numbers.
I did some manual tests and we get an improvement of roughly 2-3% |
6e65ada
to
b594443
Compare
Leverage the VIRTIO_BLK_F_FLUSH flag in order to avoid receiving flush requests when the block device uses CacheType::Unsafe. This has 2 advantages: 1. It simplifies the request execution logic a bit 2. It improves efficiency when the block device uses CacheType::Unsafe Signed-off-by: Serban Iorga <seriorga@amazon.com>
b594443
to
60ea55a
Compare
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In firecracker-microvm#2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
In #2702 the behaviour of the `Unsafe` cache type was changed. If selected the `flush` feature is not advertised to the guest. This commit just adds missing documentation change. Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
Reason for This PR
[block] simplify unsafe flush behavior
Description of Changes
Leverage the VIRTIO_BLK_F_FLUSH flag in order to avoid receiving flush
requests when the block device uses CacheType::Unsafe. This has 2
advantages:
rust-vmm
.License Acceptance
By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license.
PR Checklist
[Author TODO: Meet these criteria.]
[Reviewer TODO: Verify that these criteria are met. Request changes if not]
git commit -s
).unsafe
code is properly documented.firecracker/swagger.yaml
.CHANGELOG.md
.