From: Eric Dumazet <eric.dumazet@gmail.com>
To: Michael Chan <mchan@broadcom.com>
Cc: David Laight <David.Laight@ACULAB.COM>,
Nithin Nayak Sujir <nsujir@broadcom.com>,
davem@davemloft.net, netdev@vger.kernel.org,
stable@vger.kernel.org
Subject: RE: [PATCH v2 net 2/2] tg3: Fix data corruption on 5725 with TSO
Date: Wed, 15 May 2013 08:23:43 -0700 [thread overview]
Message-ID: <1368631423.4519.32.camel@edumazet-glaptop> (raw)
In-Reply-To: <1368630754.3768.14.camel@LTIRV-MCHAN1.corp.ad.broadcom.com>
On Wed, 2013-05-15 at 08:12 -0700, Michael Chan wrote:
>
> We will discard the packet if that happens. I think the probabilty is
> very small.
Data corruption means the content of the packet was mangled on the wire,
or was it a more serious issue, like a tx queue hang ?
next prev parent reply other threads:[~2013-05-15 15:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 21:04 [PATCH v2 net 0/2] tg3: 2 bugfixes - TSO data corruption and phy power down Nithin Nayak Sujir
2013-05-13 21:04 ` [PATCH v2 net 1/2] tg3: Skip powering down function 0 on certain serdes devices Nithin Nayak Sujir
2013-05-14 18:08 ` Joe Perches
2013-05-14 18:17 ` Nithin Nayak Sujir
2013-05-13 21:04 ` [PATCH v2 net 2/2] tg3: Fix data corruption on 5725 with TSO Nithin Nayak Sujir
2013-05-13 21:14 ` Eric Dumazet
2013-05-13 21:34 ` Nithin Nayak Sujir
2013-05-13 21:40 ` Eric Dumazet
2013-05-13 21:47 ` Nithin Nayak Sujir
2013-05-13 22:10 ` Eric Dumazet
2013-05-14 8:40 ` David Laight
2013-05-14 15:04 ` Michael Chan
2013-05-14 15:20 ` David Laight
2013-05-14 16:19 ` Michael Chan
2013-05-14 16:46 ` Eric Dumazet
2013-05-15 8:56 ` David Laight
2013-05-15 15:12 ` Michael Chan
2013-05-15 15:23 ` Eric Dumazet [this message]
2013-05-15 15:51 ` Michael Chan
2013-05-14 18:32 ` [PATCH v2 net 0/2] tg3: 2 bugfixes - TSO data corruption and phy power down 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=1368631423.4519.32.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=David.Laight@ACULAB.COM \
--cc=davem@davemloft.net \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=nsujir@broadcom.com \
--cc=stable@vger.kernel.org \
/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