netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Anders Boström" <anders@netinsight.net>
To: Jie.Yang@Atheros.com
Cc: ben@decadent.org.uk, netdev@vger.kernel.org,
	565404@bugs.debian.org, Xiong.Huang@Atheros.com
Subject: Re: Bug#565404: linux-image-2.6.26-2-amd64: atl1e: TSO is broken
Date: Wed, 20 Jan 2010 10:27:04 +0100 (CET)	[thread overview]
Message-ID: <20100120.102704.295948365864962720.anders@netinsight.net> (raw)
In-Reply-To: <CDAFEDABF718A54BABD0DA5476695307443F1E8D@SHEXMB-01.global.atheros.com>

>>>>> "JY" == Jie Yang <Jie.Yang@Atheros.com> writes:

 JY> Anders Boström <anders@netinsight.net> wrote:
 >> It is an ASUS M4A78 PRO motherboard with the Atheros
 >> AR8121/AR8113/AR8114 on-board.
 >> 
 >> >> ~25Mbyte/s performance. I get ~5000 retransmitted packets
 >> per GByte  >> data, according to RetransSegs in
 >> /proc/net/snmp . wireshark in the  >> client show that the
 >> server send out a sequence of frames. All but the  >> last
 >> one are 1500 bytes IP-packets. The last one is shorter, but
 >> the  >> IP-header still say 1500 byte. The client then
 >> requests retransmit,  >> and the retransmitted frame arrives
 >> with correct IP-header.

 JY> i just test it on Linux localhost.localdomain 2.6.31.5-127.fc12.x86_64 #1 SMP Sat Nov 7 21:11:14 EST 2009 x86_64 x86_64 x86_64 GNU/Linux.
 JY> with hardware, Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller (rev b0)
 JY> device id : 1969:1026 (rev b0)

 JY> i upload/download a 382M it work well with retransmit packet:

Have you tested NFS over TCP? The block-size the application uses can
have an effect on this. What application did you use? Block-size?

/ Anders

  reply	other threads:[~2010-01-20  9:27 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100115.142502.968775035345957525.anders@netinsight.net>
     [not found] ` <1263767939.8876.94.camel@localhost>
2010-01-18 14:43   ` Bug#565404: linux-image-2.6.26-2-amd64: atl1e: TSO is broken Anders Boström
2010-01-20  6:03     ` Jie Yang
2010-01-20  9:27       ` Anders Boström [this message]
2010-01-21  5:37         ` Jie Yang
2010-01-21 16:42           ` Anders Boström
2010-01-23 15:29             ` Ben Hutchings
2010-01-24  1:36               ` Herbert Xu
2010-01-25  5:41             ` Jie Yang
2010-01-25 15:36               ` Anders Boström
2010-01-26  2:04                 ` Jie Yang
2010-01-26  8:34                   ` Anders Boström
2013-03-31  0:25                     ` Ben Hutchings
2013-03-31  0:43                       ` Huang, Xiong
2013-03-31  1:18                       ` Huang, Xiong
2013-03-31  2:10                         ` Ben Hutchings
2013-04-01  2:51                           ` Huang, Xiong
2013-04-02 21:15                             ` Hannes Frederic Sowa
2013-04-02 21:51                               ` Huang, Xiong
2013-04-02 22:19                                 ` Hannes Frederic Sowa
2013-04-02 22:23                                   ` Huang, Xiong
2013-04-03  0:00                                     ` Hannes Frederic Sowa
2013-04-03  0:12                                       ` Huang, Xiong
2013-04-03  0:43                                         ` Hannes Frederic Sowa
2013-04-02 22:00                               ` Eric Dumazet
2013-04-02 22:15                                 ` Hannes Frederic Sowa
2013-04-02 22:34                                   ` Eric Dumazet
2013-04-02 23:24                                     ` Hannes Frederic Sowa
2013-04-03  0:38                                     ` Hannes Frederic Sowa
2013-03-31 21:11                       ` Hannes Frederic Sowa
2013-04-02  7:35                       ` Anders Boström
2013-04-02  9:41                         ` Hannes Frederic Sowa
2013-04-02 12:22                           ` Anders Boström

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=20100120.102704.295948365864962720.anders@netinsight.net \
    --to=anders@netinsight.net \
    --cc=565404@bugs.debian.org \
    --cc=Jie.Yang@Atheros.com \
    --cc=Xiong.Huang@Atheros.com \
    --cc=ben@decadent.org.uk \
    --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).