[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200905231840.45483.mb@bu3sch.de>
Date: Sat, 23 May 2009 18:40:45 +0200
From: Michael Buesch <mb@...sch.de>
To: Michael Riepe <michael.riepe@...glemail.com>
Cc: David Dillow <dave@...dillows.org>,
Francois Romieu <romieu@...zoreil.com>,
Rui Santos <rsantos@...popie.com>,
Michael Büker <m.bueker@...lin.de>,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH 2.6.30-rc4] r8169: avoid losing MSI interrupts
On Saturday 23 May 2009 17:01:36 Michael Riepe wrote:
> The client, since I wanted to measure write throughput. The server is a
> Lenovo Thinkpad T60 (e1000e driver).
>
> > I'm running the iperf server on the r8169 and get the following results:
> >
> > mb@...er:~$ iperf -c 192.168.2.50 -t120 -i10
>
> In that case, the r8169 is receiving data (which never was a problem, at
> least for me - it only lost interrupts in TX mode).
Ok, I tested the other way around and it shows the problem:
mb@...mby:~/kernel$ iperf -c 192.168.2.205 -t120 -i10
------------------------------------------------------------
Client connecting to 192.168.2.205, TCP port 5001
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.2.50 port 34788 connected with 192.168.2.205 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.0 sec 501 MBytes 420 Mbits/sec
[ 3] 10.0-20.0 sec 533 MBytes 447 Mbits/sec
[ 3] 20.0-30.0 sec 699 MBytes 587 Mbits/sec
[ 3] 30.0-40.0 sec 715 MBytes 600 Mbits/sec
[ 3] 40.0-50.0 sec 469 MBytes 394 Mbits/sec
[ 3] 50.0-60.0 sec 466 MBytes 391 Mbits/sec
[ 3] 60.0-70.0 sec 464 MBytes 389 Mbits/sec
[ 3] 70.0-80.0 sec 498 MBytes 418 Mbits/sec
[ 3] 80.0-90.0 sec 477 MBytes 400 Mbits/sec
[ 3] 90.0-100.0 sec 601 MBytes 504 Mbits/sec
[ 3] 100.0-110.0 sec 696 MBytes 584 Mbits/sec
[ 3] 110.0-120.0 sec 510 MBytes 428 Mbits/sec
[ 3] 0.0-120.0 sec 6.47 GBytes 463 Mbits/sec
--
Greetings, Michael.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists