From: Eric Dumazet <eric.dumazet@gmail.com>
To: Nick Bowler <nbowler@elliptictech.com>
Cc: Francois Romieu <romieu@fr.zoreil.com>,
netdev@vger.kernel.org,
Realtek linux nic maintainers <nic_swsd@realtek.com>
Subject: Re: Bogus frames transmitted with r8169 & fragmentation & large mtu
Date: Thu, 16 Feb 2012 05:19:23 +0100 [thread overview]
Message-ID: <1329365963.2469.8.camel@edumazet-laptop> (raw)
In-Reply-To: <20120215233408.GA8389@elliptictech.com>
Le mercredi 15 février 2012 à 18:34 -0500, Nick Bowler a écrit :
> On 2012-02-15 23:41 +0100, Francois Romieu wrote:
> > Nick Bowler <nbowler@elliptictech.com> :
> > [...]
> > > Let me know if you need any more info,
> >
> > Please send the XID line from the r8169 driver for this device.
>
> This one?
>
> [ 10.344571] r8169 0000:02:00.0: eth0: RTL8168d/8111d at 0xf8064000, bc:ae:c5:27:19:6f, XID 083000c0 IRQ 41
>
> > Did you enable some offload feature (see 'ethtool -k') ?
>
> Not beyond the defaults as far as I know. Here's the ethtool -k output:
>
> Offload parameters for p10p1:
> rx-checksumming: on
> tx-checksumming: off
> scatter-gather: off
> tcp-segmentation-offload: off
> udp-fragmentation-offload: off
> generic-segmentation-offload: off
> generic-receive-offload: on
> large-receive-offload: off
> rx-vlan-offload: on
> tx-vlan-offload: on
> ntuple-filters: off
> receive-hashing: off
>
> Thanks,
1) Are you using SLUB, SLAB, or SLOB ?
2) Problem with MTU=9000 is that frames span several 4K pages.
Maybe some versions of r8169 hardware have problems with that ...
3) We could check in xmit handler if the frames are correct before
sending them. (Adding a trace of ICMP frames, and check if the payload
is all 0x42 filler or not)
next prev parent reply other threads:[~2012-02-16 4:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 16:37 Bogus frames transmitted with r8169 & fragmentation & large mtu Nick Bowler
2012-02-15 19:13 ` Eric Dumazet
2012-02-15 19:58 ` Nick Bowler
2012-02-15 20:32 ` Nick Bowler
2012-02-15 23:23 ` Francois Romieu
2012-02-16 6:40 ` hayeswang
2012-02-16 7:46 ` Francois Romieu
2012-02-16 12:04 ` Francois Romieu
2012-02-21 2:58 ` hayeswang
2012-02-21 10:57 ` Francois Romieu
2012-02-15 22:41 ` Francois Romieu
2012-02-15 23:34 ` Nick Bowler
2012-02-16 4:19 ` Eric Dumazet [this message]
2012-02-16 16:14 ` Nick Bowler
2012-02-16 10:15 ` joeyli
2012-02-16 12:04 ` Francois Romieu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1329365963.2469.8.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=nbowler@elliptictech.com \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=romieu@fr.zoreil.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox