From: "Michael Chan" <mchan@broadcom.com>
To: "David Miller" <davem@davemloft.net>
Cc: jk@blackdown.de, linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: tg3 timeouts with 2.6.17-rc6
Date: Sat, 17 Jun 2006 11:23:28 -0700 [thread overview]
Message-ID: <1150568608.26368.49.camel@rh4> (raw)
In-Reply-To: <1551EAE59135BE47B544934E30FC4FC041BD1E@NT-IRVA-0751.brcm.ad.broadcom.com>
On Fri, 2006-06-16 at 20:37 -0700, Michael Chan wrote:
> David Miller wrote:
>
> > From: "Michael Chan" <mchan@broadcom.com>
> > Date: Fri, 16 Jun 2006 18:27:32 -0700
> >
> > > In the meantime, I wonder if we should disable TSO by default on the
> > > 5780 chip for 2.6.17.
> >
> > Sounds reasonable. Would we disable it for all chips that set
> > TG3_FLG2_5780_CLASS or a specific variant?
> >
> Yes, let's disable it for all TG3_FLG2_5780_CLASS chips for now
> until we figure out what's going on.
David, Here's the patch if you haven't already made one:
[TG3]: Disable TSO by default on 5780 class chips.
Disable TSO by default on 5780, 5714, and 5715 chips for now while we
investigate the reported tx timeouts by Juergen Kreileder. Thanks to
Juergen for reporting the problem.
Update version to 3.60.
Signed-off-by: Michael Chan <mchan@broadcom.com>
diff --git a/drivers/net/tg3.c b/drivers/net/tg3.c
index 862c226..607d87e 100644
--- a/drivers/net/tg3.c
+++ b/drivers/net/tg3.c
@@ -69,8 +69,8 @@
#define DRV_MODULE_NAME "tg3"
#define PFX DRV_MODULE_NAME ": "
-#define DRV_MODULE_VERSION "3.59"
-#define DRV_MODULE_RELDATE "June 8, 2006"
+#define DRV_MODULE_VERSION "3.60"
+#define DRV_MODULE_RELDATE "June 17, 2006"
#define TG3_DEF_MAC_MODE 0
#define TG3_DEF_RX_MODE 0
@@ -11385,7 +11385,11 @@ static int __devinit tg3_init_one(struct
* Firmware TSO on older chips gives lower performance, so it
* is off by default, but can be enabled using ethtool.
*/
- if (tp->tg3_flags2 & TG3_FLG2_HW_TSO)
+ /* Disable TSO by default on all 5780 class chips because
+ * of reported tx timeouts.
+ */
+ if ((tp->tg3_flags2 & TG3_FLG2_HW_TSO) &&
+ !(tp->tg3_flags2 & TG3_FLG2_5780_CLASS))
dev->features |= NETIF_F_TSO;
#endif
next prev parent reply other threads:[~2006-06-17 18:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-17 3:37 tg3 timeouts with 2.6.17-rc6 Michael Chan
2006-06-17 18:23 ` Michael Chan [this message]
2006-06-18 4:08 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2006-06-16 17:02 Michael Chan
2006-06-16 21:20 ` Juergen Kreileder
2006-06-16 21:42 ` Michael Chan
2006-06-17 0:05 ` Juergen Kreileder
2006-06-17 1:27 ` Michael Chan
2006-06-17 2:51 ` David Miller
2006-06-16 16:50 Juergen Kreileder
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=1150568608.26368.49.camel@rh4 \
--to=mchan@broadcom.com \
--cc=davem@davemloft.net \
--cc=jk@blackdown.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).