RFC veth, bridge, and GSO maximums
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 19 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | br: add notifier for when bridge changes it GSO maximumsinclude/ net/ | +8 | 0 replies | |
| 2/2 | veth: propagate bridge GSO to peerdrivers/ | +72 | 16 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH RFC 0/2] veth, bridge, and GSO maximums
This pair of patchesimproves the performance when running containers in an environment where underlying device has lower GSO maximum (such as Azure).
With containers a veth pair is created and one end is attached to the bridge device. The bridge device correctly reports computes GSO parameters that are the minimum of the lower devices.
The problem is that the other end of the veth device (in container) reports the full GSO size. This patch propogates the upper (bridge device) parameters to the other end of the veth device.
Please consider it as alternative to the sysfs GSO changes.
Stephen Hemminger (2):
br: add notifier for when bridge changes it GSO maximums
veth: propagate bridge GSO to peer
drivers/net/veth.c | 72 +++++++++++++++++++++++++++++++++++++++++++++++ include/linux/netdevice.h | 1 + net/bridge/br_if.c | 7 +++++ 3 files changed, 80 insertions(+)
Signature · 1 line
2.11.0