You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -93,9 +93,11 @@ make test
93
93
94
94
- VirtIO improvements:
95
95
- Abstract and improve request/response queue from rng
96
+
- Don't leak memory on purpose in virtio-blk device
96
97
- Ensure we zero out descriptors after using them so we don't accidentally reuse the buffer
97
98
- Improve memory "ownership" ergonomics, ensuring buffers are dropped after use. Maybe abstract into a common layer somehow?
98
99
- Create a physically contiguous heap, or slab allocator, or something for virtio buffer requests so we don't waste an entire page per tiny allocation.
100
+
- Ensure we are still satisfying any alignment requirements for buffers. Read the spec!
99
101
- Locking: we need to lock writes (I think?), but we should be able to read from the queue without locking. This should be ergonomic. I don't necessarily want to bury a mutex deep in the code.
100
102
- Investigate how Linux or other OS virtio drivers do locking
101
103
- Ensure we don't accidentally reuse descriptors while we are waiting for a response from the device. Don't automatically just wrap around! This is what might require a mutex rather than just atomic integers?
0 commit comments