virtio_ring: fix description of virtqueue_get_buf
The device (not the driver) populates the used ring and includes the len of how much data was written. Signed-off-by: Felipe Franciosi <felipe@nutanix.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
This commit is contained in:
parent
b9fd06d0da
commit
0c7eaf5930
@ -649,7 +649,7 @@ static inline bool more_used(const struct vring_virtqueue *vq)
|
|||||||
* @vq: the struct virtqueue we're talking about.
|
* @vq: the struct virtqueue we're talking about.
|
||||||
* @len: the length written into the buffer
|
* @len: the length written into the buffer
|
||||||
*
|
*
|
||||||
* If the driver wrote data into the buffer, @len will be set to the
|
* If the device wrote data into the buffer, @len will be set to the
|
||||||
* amount written. This means you don't need to clear the buffer
|
* amount written. This means you don't need to clear the buffer
|
||||||
* beforehand to ensure there's no data leakage in the case of short
|
* beforehand to ensure there's no data leakage in the case of short
|
||||||
* writes.
|
* writes.
|
||||||
|
Loading…
Reference in New Issue
Block a user