Sorry, I think this is not a kernel related problem rather than problem in
UDP bandwidth:


[root@ABC iperf-2.0.5]# iperf -c XYZ
------------------------------------------------------------
Client connecting to ca-ostest193, TCP port 5001
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 139.185.50.70 port 56604 connected with 139.185.48.193 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec  1.10 GBytes   942 Mbits/sec
[root@ca-ostest286 iperf-2.0.5]#
[root@ca-ostest286 iperf-2.0.5]#

[root@ABC iperf-2.0.5]# iperf -c XYZ -u
------------------------------------------------------------
Client connecting to ca-ostest193, UDP port 5001
Sending 1470 byte datagrams
UDP buffer size:  111 KByte (default)
------------------------------------------------------------
[  3] local 139.185.50.70 port 55770 connected with 139.185.48.193 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec  60.0 GBytes  51.5 Gbits/sec
[  3] Sent 893 datagrams
read failed: Connection refused
[  3] WARNING: did not receive ack of last datagram after 5 tries.




[root@ABC iperf-2.0.5]# ethtool eth3
Settings for eth3:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        MDI-X: Unknown
        Supports Wake-on: g
        Wake-on: d
        Link detected: yes





On Tue, Apr 26, 2011 at 3:19 PM, er krishna <erkris...@gmail.com> wrote:

> Hi All,
>
> I am trying to use iperf on RHEL 6 and I am getting wrong result in UDP
> case. My network max spped is 1gbp/s , but with 2.6.32 kernel it is giving
> me 38 gbp/s. With 2.6.18 kernel I was getting ~800 mbp/s speed. Following
> command has run for client:
>
>  [root@pvm61ext3 iperf-2.0.5]# iperf -c 139.185.51.53  -u -b 300M
> ------------------------------------------------------------
> Client connecting to 139.185.51.53, UDP port 5001
> Sending 1470 byte datagrams
> UDP buffer size:  256 KByte (default)
> ------------------------------------------------------------
> [  3] local 139.185.48.101 port 6574 connected with 139.185.51.53 port 5001
> [ ID] Interval       Transfer     Bandwidth
> [  3]  0.0-10.0 sec  44.4 GBytes  38.1 Gbits/sec
> [  3] Sent 256383 datagrams
> read failed: Connection refused
> [  3] WARNING: did not receive ack of last datagram after 2 tries.
>
>
> Following command has run for server:
>
> [root@pvm61ocfs iperf-2.0.5]# iperf -s -w 128k
>
>
> Can anybody please help me here to understand why it is happening. Is this
> a kernel bug or iperf bug ?
>
>
> Krishna
>
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Iperf-users mailing list
Iperf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/iperf-users

Reply via email to