On (Fri) 06 Jul 2012 [16:07:06], Amit Shah wrote:
> The current virtqueue_avail_bytes() is a weird API: it's oddly-named:
> doesn't tell us what the API is going to do, and also suits just one
> use-case (that in virtio-net.c).
>
> Introduce virtqueue_get_avail_bytes(), which returns the number of
On (Fri) 06 Jul 2012 [16:07:06], Amit Shah wrote:
> The current virtqueue_avail_bytes() is a weird API: it's oddly-named:
> doesn't tell us what the API is going to do, and also suits just one
> use-case (that in virtio-net.c).
>
> Introduce virtqueue_get_avail_bytes(), which returns the number of
The current virtqueue_avail_bytes() is a weird API: it's oddly-named:
doesn't tell us what the API is going to do, and also suits just one
use-case (that in virtio-net.c).
Introduce virtqueue_get_avail_bytes(), which returns the number of
bytes in the vq available for input as well as output.
virt
