[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1203448265.13495.95.camel@dell>
Date: Tue, 19 Feb 2008 11:11:05 -0800
From: "Michael Chan" <mchan@...adcom.com>
To: "Tony Battersby" <tonyb@...ernetics.com>
cc: "David Miller" <davem@...emloft.net>, herbert@...dor.apana.org.au,
netdev <netdev@...r.kernel.org>, gregkh@...e.de,
linux-kernel@...r.kernel.org
Subject: Re: TG3 network data corruption regression 2.6.24/2.6.23.4
On Tue, 2008-02-19 at 11:16 -0500, Tony Battersby wrote:
> iSCSI
> performance drops to 6 - 15 MB/s when the 3Com NIC is doing heavy rx
> with light tx,
That's strange. The patch should only affect TX performance slightly
since we are just turning off SG for TX. Please take an ethereal trace
to see what's happening and compare with a good trace.
> but remains at a decent 115 MB/s when the 3Com NIC is
> doing heavy tx with light rx. When I revert Herbert's patch instead
> of
> applying the patch above, I get 115 MB/s in both cases. (With a stock
> unpatched kernel, the test fails almost immediately because the iSCSI
> control PDUs are corrupted, causing the TCP connection to be dropped.)
>
> The SysKonnect NIC that does not exhibit this problem has a chip that
> says "BCM5411KQM" "TT0128 P2Q" and "56975E".
>
I think this is the 5700, but please send me the tg3 output that
identifies the chip and the revision. Something like this:
eth2: Tigon3 [partno(BCM95705) rev 3003 PHY(5705)] (PCI:66MHz:32-bit) 10/100/1000Base-T Ethernet 00:10:18:04:57:0d
eth2: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[0] TSOcap[1]
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists