Add packed virtqueue support #301
Open
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.
Summary of the PR
Adds support for packed virtqueues, implementing the VirtIO packed virtqueue format alongside the existing split virtqueue support. Packed virtqueues offer improved performance through better cache locality and reduced memory overhead compared to traditional split virtqueues.
Changes:
- Updated documentation to clearly distinguish between split and packed virtqueue address semantics
- For packed virtqueues: desc_table_addr becomes the packed descriptor ring, used_ring_addr becomes driver event suppression, avail_ring_addr becomes device event suppression
- Added RING_PACKED feature flag (bit 34, value 0x4_0000_0000)
- Added VHOST_VRING_F_PACKED vring flag (bit 1, value 0x2)
- Implemented packed virtqueue inflight I/O structures (DescStatePacked, QueueRegionPacked)
- Extended kernel backend to support packed virtqueue address configuration
- Added handling of packed layout in vring setup
- Added test_packed_virtqueue_features() to validate feature flag definitions
- Added test_packed_vring_addr_validation() to test packed virtqueue address validation/alignment
Requirements
Before submitting your PR, please make sure you addressed the following
requirements:
git commit -s
), and the commit message has max 60 characters for thesummary and max 75 characters for each description line.
test.
Release" section of CHANGELOG.md (if no such section exists, please create one).
unsafe
code is properly documented.