Cathy Zhou writes: > My personal take is that this is due to GLDv3 does not support HW VLAN tag > insertion/removal, so that such driver has to do the parsing/encoding > itself. Ideally, this parsing/encoding should be done by the GLDv3 framework.
If and when GLDv3 grows the ability to parse/encode VLAN tags, I really hope that it is optional and not tied to however the "margin" is treated. My 10GbE NIC does not do HW VLAN tag insertion/removal (we concluded there was no performance benefit). On several OSes, I'm forced to claim the device does HW VLAN tag support (and do tag insertion/removal in the driver) to gain support for the 4 bytes of "margin" (1518, 9018), and/or to get the OS to trust that my device can offload checksum in combination with VLAN frames. Drew _______________________________________________ networking-discuss mailing list [email protected]
