.. I think you're misunderstanding how PMTU discovery works.
The _point_ is that you refuse to send said frame in the first place.
Any number of intermediary L2 devices may decide to drop your jumbo
TX'ed frame and not generate an ICMP error message, thus breaking PMTU
discovery anyway.
In any
On 4/28/12 3:04 AM, YongHyeon PYUN wrote:
On Thu, Apr 26, 2012 at 03:23:19PM +0400, Andrey Zonov wrote:
Hi,
I found that jumbo frames don't work after r218423 with bce driver.
This happens because controller doesn't do reinitialization when MTU
is changed. Attached patch solves this problem.
On Thu, Apr 26, 2012 at 03:23:19PM +0400, Andrey Zonov wrote:
Hi,
I found that jumbo frames don't work after r218423 with bce driver.
This happens because controller doesn't do reinitialization when MTU
is changed. Attached patch solves this problem.
Could you verify whether attached
I also don't understand why sysctl hw.bce.loose_rx_mtu doesn't respect
with tunnable hw.bce.strict_rx_mtu. Is there any reason to give them
different names?
It may be an oversight. Personally I don't see any reason except
debugging purpose to limit RX frame size to interface MTU. It makes
