Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 15 Dec 2021 16:15:40 +0000
From:      bugzilla-noreply@freebsd.org
To:        net@FreeBSD.org
Subject:   [Bug 260260] igb(4) I35{0,4} parrent <--> vlan jumbo frame mtu mismatch
Message-ID:  <bug-260260-7501-p9rr5rnbmD@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-260260-7501@https.bugs.freebsd.org/bugzilla/>
References:  <bug-260260-7501@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D260260

--- Comment #4 from Marek Zarychta <zarychtam@plan-b.pwste.edu.pl> ---
I was told to update the PR with some em vs igb details, so TL;DR:
1. em(4) works like before with the same MTU 9000 on parent em(4), lagg(4) =
and
vlan(4) with the options: VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,VLAN_HWFILTER
enabled.
2. igb(4) doesn't work this way and with options:
VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWFILTER,VLAN_HWTSO enab=
led,
the size of vlan(4) MTU has to be lowered by 4 bytes to unbreak receiving j=
umbo
frames.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-260260-7501-p9rr5rnbmD>