Bug 440035
| Summary: | why do Xen virtual interfaces try and do tx-checksumming? | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Chris Stankaitis <cstankaitis> |
| Component: | xen | Assignee: | Xen Maintainance List <xen-maint> |
| Status: | CLOSED NOTABUG | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 5.1 | ||
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-04-01 14:39:52 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Chris Stankaitis
2008-04-01 14:32:53 UTC
The Xen VIF kernel driver *does* support tx-checksumming, in so much as it will pass packets straight through to the host NIC for checksumming & fragmentation. For guest<->guest traffic this allows checksumming/fragmentation overhead to be avoided entirely. This results in a throughput improvements over > x100. If you have specific scenarios in which tx checksumming causes problems please enter a bug providing details of exactly what is broken & the steps to reproduce the problem. |