Jon, Marc: thank you for information! I modified following kernel parameters:
#UDP socket receive buffer net.ipv4.udp_rmem_min #UDP socket send buffer net.ipv4.udp_wmem_min #TCP socket receive max buffer size net.core.rmem_max #TCP socket send max buffer size net.core.wmem_max ..under Debian like this(all values are in bytes): test: ~# sysctl -w net.ipv4.udp_rmem_min=4194304 net.ipv4.udp_rmem_min = 4194304 test: ~# sysctl -w net.ipv4.udp_wmem_min=4194304 net.ipv4.udp_wmem_min = 4194304 test: ~# sysctl -w net.core.rmem_max=8388608 net.core.rmem_max = 8388608 test: ~# sysctl -w net.core.wmem_max=8388608 net.core.wmem_max = 8388608 test: ~# Please correct me if those kernel parameters are not the correct ones(I doubt about "net.ipv4.udp_rmem_min" and "net.ipv4.udp_wmem_min" because of "_min") or if values are stupid. However, I managed to start both Iperf server and client in both TCP and UDP mode with increased buffer values: example 1: test: ~# iperf -c 192.168.1.68 -fm -u -b 10M -d -w 2M ------------------------------------------------------------ Server listening on UDP port 5001 Receiving 1470 byte datagrams UDP buffer size: 4.00 MByte (WARNING: requested 2.00 MByte) ------------------------------------------------------------ ------------------------------------------------------------ Client connecting to 192.168.1.68, UDP port 5001 Sending 1470 byte datagrams UDP buffer size: 4.00 MByte (WARNING: requested 2.00 MByte) ------------------------------------------------------------ [ 4] local 192.168.1.68 port 58601 connected with 192.168.1.68 port 5001 [ 3] local 192.168.1.68 port 5001 connected with 192.168.1.68 port 58601 example 2: test: ~# iperf -s -fm -w 4M ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 8.00 MByte (WARNING: requested 4.00 MByte) ------------------------------------------------------------ One more thing- whats with the double values? I mean why are buffer values provided by kernel always double the size of the requested buffer values? regards, martin 2011/4/4 Marc Herbert <[email protected]>: > On Mon, 4 Apr 2011, Martin T wrote: > >> If I execute Iperf(version 2.0.5 (08 Jul 2010) pthreads) client with >> "iperf -c 192.168.2.1 -u -fm -t60 -d -b 10m -w 4m" command, Iperf >> server with "iperf -s u -w 4m" command, Iperf client with "iperf -c >> 192.168.1.1 -t 60 -w 2m" command etc, I get the "TCP window size: 50.0 >> KByte (WARNING: requested 2.00 MByte)", "UDP buffer size: 0.01 MByte >> (WARNING: requested 4.00 MByte)" or similar warning. > > > This warning message means that your operating system denies the > request from iperf. Probably because your request is deemed too big > and would consume too much kernel memory. You either need to configure > your operating system to be more generous, or be less greedy yourself. > > > Marc. > ------------------------------------------------------------------------------ Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev _______________________________________________ Iperf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/iperf-users
