Change Details

Support for virtio-net mergeable rx buffers feature was added in r354552. So far, this feature was enabled only with the vale(4) backend, since it helps in case of large TSO packets. However, the same feature is also useful with the tap backend (which does not currently support TSO), when Jumbo frames configured. This patch adds a command line option to force a virtio-net device to enable or disable the mergeable rx buffers feature, regardless of the net backend used.

This patch cleans up the API between the net frontends (e1000, virtio-net) and the net backends (tap and netmap). We move the virtio-net header stripping/prepending to the virtio-net code, where this functionality belongs. In this way, the netbe_send() and netbe_recv() signatures can have `const struct iov *` rather than `struct iov *`.

Support for virtio-net mergeable rx buffers feature was added in r354552This patch cleans up the API between the net frontends (e1000, virtio-net) and the net backends (tap and netmap). So far, this feature was enabled only withWe move the virtio-net header stripping/prepending to the vale(4) backendirtio-net code, since it helps in case of large TSO packetswhere this functionality belongs. However, the same feature is also useful with the tap backend (which does not currently support TSO), when Jumbo frames configured. This patch adds a command line option to force a virtio-net device to enable or disable the mergeable rx buffers featureIn this way, regardless of the net backend usedthe netbe_send() and netbe_recv() signatures can have `const struct iov *` rather than `struct iov *`.