On Tue, Dec 12, 2017 at 8:13 AM, Ed Swierk <eswi...@skyportsystems.com> wrote: > Most physical Ethernet devices pad short packets to the minimum length > of 64 bytes (including FCS) on transmit. It can be useful to simulate > this behavior when debugging a problem that results from it (such as > incorrect L4 checksum calculation). > > Padding is unnecessary for most applications so leave it off by > default. Enable padding only when the otherwise unused IFF_AUTOMEDIA > flag is set (e.g. by writing 0x5003 to flags in sysfs).
This doesn't make sense, why should veth hot path be punished for such an unusual flag which it doesn't care? Also, why should we allow setting this flag via sysfs for veth from the beginning?
