Summary: | Performance regression in em(4) driver with bridge/tap and used with bhyve | ||||||
---|---|---|---|---|---|---|---|
Product: | Base System | Reporter: | Jason Tubnor <jason> | ||||
Component: | kern | Assignee: | freebsd-net (Nobody) <net> | ||||
Status: | Open --- | ||||||
Severity: | Affects Some People | CC: | allanjude, bwidawsk, d8zNeCFG, grehan, net, sbruno, virtualization | ||||
Priority: | --- | Keywords: | IntelNetworking, bhyve, performance, regression | ||||
Version: | 12.0-RELEASE | ||||||
Hardware: | amd64 | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
Jason Tubnor
2019-01-01 22:58:41 UTC
This might be related to bug #235031 and bug #234520. -- Martin Jason, would you be able to post your ifconfig output ? I think it will show LRO enabled on VLAN interfaces, when it should be disabled (and also on the parent VLAN interface) when it's added to a bridge group. The reason that hwvlantag will cause LRO is that stripping the VLAN tag will result in the iflib ethertype check of v4/v6 succeeding. However, this is only if LRO is enabled on an interface, which I think should not be the case from the bridge addition above. Created attachment 218374 [details]
ifconfig parent, vlan and bridges
Attached is the output. LRO isn't stripped from the parent when it or a vlan is added to a bridge. I have forced -lro at boot to ensure traffic isn't impacted ongoing. The included sample will show that vlanhwtag is now enabled.
|