diff options
author | Michael S. Tsirkin <mst@redhat.com> | 2011-07-18 03:48:46 +0000 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2011-07-18 10:42:32 -0700 |
commit | bab632d69ee48a106e779b60cc01adfe80a72807 (patch) | |
tree | 56b8bd3df85cfee8e425abe18963e5aad015e2fa /security | |
parent | 5c74501f76360ce6f410730b9b5e5976f38e8504 (diff) | |
download | op-kernel-dev-bab632d69ee48a106e779b60cc01adfe80a72807.zip op-kernel-dev-bab632d69ee48a106e779b60cc01adfe80a72807.tar.gz |
vhost: vhost TX zero-copy support
>From: Shirley Ma <mashirle@us.ibm.com>
This adds experimental zero copy support in vhost-net,
disabled by default. To enable, set
experimental_zcopytx module option to 1.
This patch maintains the outstanding userspace buffers in the
sequence it is delivered to vhost. The outstanding userspace buffers
will be marked as done once the lower device buffers DMA has finished.
This is monitored through last reference of kfree_skb callback. Two
buffer indices are used for this purpose.
The vhost-net device passes the userspace buffers info to lower device
skb through message control. DMA done status check and guest
notification are handled by handle_tx: in the worst case is all buffers
in the vq are in pending/done status, so we need to notify guest to
release DMA done buffers first before we get any new buffers from the
vq.
One known problem is that if the guest stops submitting
buffers, buffers might never get used until some
further action, e.g. device reset. This does not
seem to affect linux guests.
Signed-off-by: Shirley <xma@us.ibm.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions