On 2014-07-26, def wrote:
> Change in max_std_mtu of if_bnxreg to 9000 (and appropriate max
> eth mtu to 9018, etc) didnt make mtu to be allowed higher than 1500
> via ifconfig (invalid argument error). Moreover max hw mtu is still
> displayed as 1500 in ifconfig bnx hwfeatures.
It needs more cha
ok doing 'make' for bnx mtu right now.
I knew that its configurable via rebuild, but if standard max value was not set
by 5.5, does it mean that it can be turn on safely for kernel or for hw tx/rx
rings, memory pages, etc..?
I have some time before install the box to production, so i can try 577
Change in max_std_mtu of if_bnxreg to 9000 (and appropriate max eth mtu to
9018, etc) didnt make mtu to be allowed higher than 1500 via ifconfig (invalid
argument error). Moreover max hw mtu is still displayed as 1500 in ifconfig bnx
hwfeatures.
Maybe i missed something?
Птн 25 Июл 2014 14:43
On 24 Jul 2014, at 19:37, def wrote:
> Hi!
>
> Currently using 5.5-stable and It seems (as per hwfeatures) that driver for
> BCM 5709 (1GE dual port adapter)
> doesnt support jumbo frames at all which is critical for activation mpls on
> bnx.
> The card supports jumbo itself.
> Return invalid
Hi!
Currently using 5.5-stable and It seems (as per hwfeatures) that driver for BCM
5709 (1GE dual port adapter)
doesnt support jumbo frames at all which is critical for activation mpls on bnx.
The card supports jumbo itself.
Return invalid argument when trying to setup jumbo via ifconfig.
is th
5 matches
Mail list logo
