From: Fran├žois Romieu on
Neil Horman <nhorman(a)redhat.com> :
[...]
> +1 I wouldn't be suprised if using something over the nominal 1522 byte frame
> length on r8169 caused tx errors. The driver doesn't seem to support Jumbo
> frames, so my guess is you have to keep the packet size below 1522 bytes.

-1

The driver does not support Jumbo frames because the original 8169 will not
go much beyond 7200 (see r8169.c::SafeMtu and netdev circa 2004 december 7).

/me checks... Apparently it still works a bit.

Sergey, can you 'dmesg | grep XID' and send the output of a lspci as
well as the MTU used during the test ?

--
Ueimor
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Sergey Senozhatsky on
Hello,

On (03/31/10 22:14), Fran├žois Romieu wrote:
> -1
>
> The driver does not support Jumbo frames because the original 8169 will not
> go much beyond 7200 (see r8169.c::SafeMtu and netdev circa 2004 december 7).
>
> /me checks... Apparently it still works a bit.
>

> Sergey, can you 'dmesg | grep XID' and send the output of a lspci as
> well as the MTU used during the test ?
>

Sure.

dmesg | grep XID
[ 11.761633] r8169 0000:02:00.0: eth0: RTL8168b/8111b at 0xfd1da000, 00:1a:92:c9:a0:68, XID 18000000 IRQ 28


Sergey
First  |  Prev  | 
Pages: 1 2
Prev: (none)
Next: vbus: update gfp/slab.h includes