Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Alex Dubov <oakad@yahoo.com>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
	netdev@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: Bad TCP timestamps on non-PC platforms
Date: Mon, 10 Jan 2011 08:07:56 +0100	[thread overview]
Message-ID: <1294643276.2709.877.camel@edumazet-laptop> (raw)
In-Reply-To: <373539.88491.qm@web37603.mail.mud.yahoo.com>

Le dimanche 09 janvier 2011 à 22:33 -0800, Alex Dubov a écrit :
> > > Any ideas where this particular problem may
> > originate?
> > 
> > Is there a bug in checksum offload in the driver?
> > Does the hardware correctly handle checksum of packets that
> > are
> > unaligned or whose length is an odd number of bytes?
> > 
> > If the hardware can't do checksum correctly, the driver
> > should either
> > disable checksum offload or in worst case copy the packet
> > to a new
> > buffer that is in a known safe place.
> 
> I managed to work around the issue by clearing the NETIF_F_IP_CSUM
> feature flag of the gianfar network driver, so it appears the bug is
> indeed somewhere there.
> 

Its incredible how TCP timestamps can be "usual suspects" ;)




  reply	other threads:[~2011-01-10  7:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-10  3:41 Bad TCP timestamps on non-PC platforms Alex Dubov
2011-01-10  3:57 ` Stephen Hemminger
2011-01-10  6:33   ` Alex Dubov
2011-01-10  7:07     ` Eric Dumazet [this message]
2011-01-10  7:19       ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2011-01-06  6:55 Alex Dubov
2011-01-06  8:09 ` Eric Dumazet
2011-01-07  1:55   ` Alex Dubov
2011-01-07  2:11     ` Eric Dumazet
2011-01-07  6:39       ` Alex Dubov
2011-01-06 16:44 ` David Miller

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=1294643276.2709.877.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=oakad@yahoo.com \
    --cc=shemminger@vyatta.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