| commit | 5539ae9613587e4a4eec42d420b8bdd9ff552a65 | |
| author | Rusty Russell <rusty@rustcorp.com.au> | |
| Sat, 3 May 2008 02:50:46 +0000 (2 21:50 -0500) | ||
| committer | Rusty Russell <rusty@rustcorp.com.au> | |
| Fri, 2 May 2008 11:50:47 +0000 (2 21:50 +1000) | ||
| tree | 39db7c012bed1b364069c0b9b2bdd5ece87210b1 | treesnapshot (tar.gz zip) |
| parent | 99ffc696d10b28580fe93441d627cf290ac4484c | commitdiff |
virtio: finer-grained features for virtio_net
So, we previously had a 'VIRTIO_NET_F_GSO' bit which meant that 'the
host can handle csum offload, and any TSO (v4&v6 incl ECN) or UFO
packets you might want to send. I thought this was good enough for
Linux, but it actually isn't, since we don't do UFO in software.
So, add separate feature bits for what the host can handle. Add
equivalent ones for the guest to say what it can handle, because LRO
is coming too (thanks Herbert!).
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
So, we previously had a 'VIRTIO_NET_F_GSO' bit which meant that 'the
host can handle csum offload, and any TSO (v4&v6 incl ECN) or UFO
packets you might want to send. I thought this was good enough for
Linux, but it actually isn't, since we don't do UFO in software.
So, add separate feature bits for what the host can handle. Add
equivalent ones for the guest to say what it can handle, because LRO
is coming too (thanks Herbert!).
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
| drivers/net/virtio_net.c | diffblobblamehistory | |
| include/linux/virtio_net.h | diffblobblamehistory |