[blk-threaded - 1/12] block: separate configuration from runtime resources - #6123
Open
PierreBertholom wants to merge 1 commit into
Open
[blk-threaded - 1/12] block: separate configuration from runtime resources#6123PierreBertholom wants to merge 1 commit into
PierreBertholom wants to merge 1 commit into
Conversation
Keep block configuration in VirtioBlockConfig and remove duplicated fields. Move queues, eventfds, disk, and rate-limiter state to BlockResources. Keep configuration synchronized across runtime updates and snapshot restore. This prepares runtime resources to move to a worker thread. Signed-off-by: Pierre Bertholom <pbertho@amazon.com>
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## feature/virtio-blk-threaded #6123 +/- ##
===============================================================
+ Coverage 82.60% 82.61% +0.01%
===============================================================
Files 277 277
Lines 30942 30966 +24
===============================================================
+ Hits 25559 25583 +24
Misses 5383 5383
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This was referenced Aug 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stack
This pull request starts a 12-part stack and builds on #6053.
The stack adds an optional dedicated worker thread for each virtio-block device.
When threaded mode is enabled, the worker owns the data-path resources and processes I/O outside the VMM thread.
This design lets block I/O run in parallel with other VMM work and reduces contention on the VMM thread.
When threaded mode is disabled, the device keeps the current inline behavior and processes I/O on the VMM thread.
The stack adds the full worker lifecycle, runtime updates, snapshot support, seccomp policy, API configuration, and test coverage.
Changes
Keep block configuration in
VirtioBlockConfigand remove duplicated fields.Move queues, eventfds, disk, and rate-limiter state to
BlockResources.Keep configuration synchronized across runtime updates and snapshot restore.
This prepares runtime resources to move to a worker thread.