diff options
| author | Michael S. Tsirkin <mst@redhat.com> | 2017-03-28 02:09:11 +0300 |
|---|---|---|
| committer | Cornelia Huck <cohuck@redhat.com> | 2017-09-11 12:56:48 +0200 |
| commit | 4efd3039157024ea53c927cf5c764f1fa9c5266b (patch) | |
| tree | 500619cfd3f415e159a275c25fe62f8c70066b4d /t4ht-workaround/t4ht | |
| parent | 81e0eeca43d4c61927e16e52fbc8556a71714e64 (diff) | |
net: clarify device rules for mergeable buffers
The idea behind mergeable buffers was to simply use them in a way
similar to a chain of descriptors. Unfortunately the current text does
not say so - apparently nothing says device can't spread a packet over
as many buffers as it likes - but this didn't prevent drivers from
relying on buffers being used as a chain of descriptors, completely -
and blindly accessing it without checking the length at least for the
packet header.
Let's just make the spec match this reality - if devices ever want more
flexibility, we can add a feature bit.
Further, correct all misuses of a "descriptor" to "buffer" as that
is the entity that is being merged.
VIRTIO-160
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Message-Id: <1490655576-12173-1-git-send-email-mst@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
Diffstat (limited to 't4ht-workaround/t4ht')
0 files changed, 0 insertions, 0 deletions