Re: b44: regression in 2.6.22 (resend)

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Michael Buesch <mb@...>
Cc: linux-kernel <linux-kernel@...>, linux-wireless <linux-wireless@...>, Stephen Hemminger <shemminger@...>, Arnaldo Carvalho de Melo <acme@...>, Jeff Garzik <jgarzik@...>, Gary Zambrano <zambrano@...>, <netdev@...>, Andrew Morton <akpm@...>
Date: Sunday, May 27, 2007 - 6:15 pm

On Sunday 27 May 2007, Michael Buesch wrote:
2.6.21.1:

[  5] local 192.168.1.2 port 54423 connected with 192.168.1.1 port 5001
[  5]  0.0-60.3 sec  3.06 MBytes    426 Kbits/sec
[  4] local 192.168.1.2 port 5001 connected with 192.168.1.1 port 41053
[  4]  0.0-163.0 sec    130 MBytes  6.67 Mbits/sec


2.6.22-rc3:

[  5] local 192.168.1.2 port 46002 connected with 192.168.1.1 port 5001
[  5]  0.0-61.5 sec  84.0 MBytes  11.5 Mbits/sec
[  4] local 192.168.1.2 port 5001 connected with 192.168.1.1 port 44379
[  4]  0.0-93.8 sec  30.6 MBytes  2.74 Mbits/sec

=46or TX the iperf server reports the same values as the client (all values=
 are=20
from the client) but for RX they are differen:

2.6.21.1: (iperf server log):

[  5] local 192.168.1.1 port 5001 connected with 192.168.1.2 port 54423
[  5]  0.0-60.5 sec  3.06 MBytes    425 Kbits/sec
[  5] local 192.168.1.1 port 41053 connected with 192.168.1.2 port 5001
[  5]  0.0-63.1 sec    130 MBytes  17.2 Mbits/sec


2.6.22-rc3 (iperf server log):

[  4] local 192.168.1.1 port 5001 connected with 192.168.1.2 port 46002
[  4]  0.0-61.6 sec  84.0 MBytes  11.5 Mbits/sec
[  4] local 192.168.1.1 port 44379 connected with 192.168.1.2 port 5001
[  4]  0.0-63.3 sec  30.6 MBytes  4.06 Mbits/sec

I have no idea how iperf internally works and what can cause such different=
=20
results here.

00
00
et
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: b44: regression in 2.6.22 (resend), Maximilian Engelhardt, (Sun May 27, 3:25 pm)
Re: b44: regression in 2.6.22 (resend), Michael Buesch, (Sun May 27, 5:13 pm)
Re: b44: regression in 2.6.22 (resend), Maximilian Engelhardt, (Sun May 27, 6:15 pm)
Re: b44: regression in 2.6.22 (resend), Michael Buesch, (Sun May 27, 8:24 pm)
Re: b44: regression in 2.6.22 (resend), Maximilian Engelhardt, (Sun May 27, 8:40 pm)
Re: b44: regression in 2.6.22 (resend), Michael Buesch, (Mon May 28, 6:49 am)
Re: b44: regression in 2.6.22 (resend), Maximilian Engelhardt, (Mon May 28, 10:12 am)
Re: b44: regression in 2.6.22 (resend), Michael Buesch, (Mon May 28, 10:55 am)
Re: b44: regression in 2.6.22 (resend), Gary Zambrano, (Tue May 29, 10:14 am)
Re: b44: regression in 2.6.22 (resend), Michael Buesch, (Tue May 29, 4:45 pm)
Re: b44: regression in 2.6.22 (resend), Gary Zambrano, (Tue May 29, 5:05 pm)
Re: b44: regression in 2.6.22 (resend), Jeff Garzik, (Tue May 29, 6:39 pm)
Re: b44: regression in 2.6.22 (resend), Gary Zambrano, (Tue May 29, 5:36 pm)
Re: b44: regression in 2.6.22 (resend), Michael Buesch, (Wed May 30, 6:45 am)
Re: b44: regression in 2.6.22 (resend), Stephen Hemminger, (Tue May 29, 5:01 pm)
Re: b44: regression in 2.6.22 (resend), Michael Buesch, (Mon May 28, 6:16 am)
Re: b44: regression in 2.6.22 (resend), Maximilian Engelhardt, (Mon May 28, 10:09 am)
Re: b44: regression in 2.6.22 (resend), Michael Buesch, (Mon May 28, 11:14 am)
Re: b44: regression in 2.6.22 (resend), Thomas Gleixner, (Mon May 28, 11:32 am)
Re: b44: regression in 2.6.22 (resend), Maximilian Engelhardt, (Mon May 28, 1:44 pm)
Re: b44: regression in 2.6.22 (resend), Thomas Gleixner, (Mon May 28, 3:23 pm)
Re: b44: regression in 2.6.22 (resend), Maximilian Engelhardt, (Sun Jun 3, 12:26 pm)
Re: b44: regression in 2.6.22 (resend), Thomas Gleixner, (Mon Jun 4, 2:39 am)
Re: b44: regression in 2.6.22 (resend), Stephen Hemminger, (Mon Jun 4, 12:09 pm)
Re: b44: regression in 2.6.22 (resend), Thomas Gleixner, (Mon Jun 4, 12:35 pm)
iperf: performance regression (was b44 driver problem?), Stephen Hemminger, (Mon Jun 4, 12:59 pm)
Re: iperf: performance regression (was b44 driver problem?), Stephen Hemminger, (Mon Jun 4, 1:51 pm)
Re: iperf: performance regression (was b44 driver problem?), Maximilian Engelhardt, (Mon Jun 4, 3:47 pm)
Re: iperf: performance regression (was b44 driver problem?), Stephen Hemminger, (Mon Jun 4, 4:02 pm)
Re: iperf: performance regression (was b44 driver problem?), Maximilian Engelhardt, (Mon Jun 4, 4:52 pm)
Re: b44: regression in 2.6.22 (resend), Maximilian Engelhardt, (Mon May 28, 4:55 pm)
Re: b44: regression in 2.6.22 (resend), Gary Zambrano, (Tue May 29, 9:58 am)
Re: b44: regression in 2.6.22 (resend), Maximilian Engelhardt, (Tue May 29, 1:23 pm)
Re: b44: regression in 2.6.22 (resend), Thomas Gleixner, (Mon May 28, 5:45 pm)
Re: b44: regression in 2.6.22 (resend), Maximilian Engelhardt, (Tue May 29, 2:28 pm)
Re: b44: regression in 2.6.22 (resend), Michael Buesch, (Mon May 28, 11:43 am)
Re: b44: regression in 2.6.22 (resend), Michael Buesch, (Sun May 27, 5:16 pm)
Re: b44: regression in 2.6.22 (resend), Maximilian Engelhardt, (Sun May 27, 5:50 pm)
Re: b44: regression in 2.6.22 (resend), Michael Buesch, (Sun May 27, 3:45 pm)
Re: b44: regression in 2.6.22 (resend), Maximilian Engelhardt, (Sun May 27, 4:36 pm)
Re: b44: regression in 2.6.22 (resend), Michael Buesch, (Sun May 27, 4:46 pm)
Re: b44: regression in 2.6.22 (resend), Maximilian Engelhardt, (Sun May 27, 5:46 pm)