aboutsummaryrefslogtreecommitdiffstats
path: root/.hgtags
diff options
context:
space:
mode:
authorkaf24@firebug.cl.cam.ac.uk <kaf24@firebug.cl.cam.ac.uk>2006-04-02 16:16:53 +0100
committerkaf24@firebug.cl.cam.ac.uk <kaf24@firebug.cl.cam.ac.uk>2006-04-02 16:16:53 +0100
commit0c48c2080d16c59c41ce24bc0ade4f03fbf200e0 (patch)
tree9f378f18a78aac6d1acb9c8ac6ee1010571f0035 /.hgtags
parent10daa80b938a274eec3e471ad8891ffcb49d065b (diff)
downloadxen-0c48c2080d16c59c41ce24bc0ade4f03fbf200e0.tar.gz
xen-0c48c2080d16c59c41ce24bc0ade4f03fbf200e0.tar.bz2
xen-0c48c2080d16c59c41ce24bc0ade4f03fbf200e0.zip
Make checksum handling in the virtual network drivers more robust.
Largely this involves making the logic symmetrical: for example, not only should netfront be able to tell netback that a packet has an empty protocol checksum field, but the reverse must also be true. Another change is that the drivers only advertise IP checksum offload functionality. There is currently no information propagated across the device channel about the offset of the protocol-specific checksum field. Therefore it is not safe to defer checksum calculation for protocols the remote end may not understand -- it will end up dropping having to drop the packet. Yet another change is to allow netback to disable tx checksum offload, just as we already could for netfront. Currently there is no support for disabling rx checksum offload -- that would seem to require some way of propagating the checksum-offload advertisement (or lack of it) across the device channel, as it really ought to be the transmitter that acts on it. Thanks to Ian Jackson for pointing out some of the problems with our checksum-offload handling. Several of the changes here are due to his comments. Signed-off-by: Keir Fraser <keir@xensource.com>
Diffstat (limited to '.hgtags')
0 files changed, 0 insertions, 0 deletions