[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080708134845.2372a483@speedy>
Date: Tue, 8 Jul 2008 13:48:45 -0700
From: Stephen Hemminger <stephen.hemminger@...tta.com>
To: Roland Dreier <rdreier@...co.com>
Cc: Bill Fink <billfink@...dspring.com>,
Evgeniy Polyakov <johnpol@....mipt.ru>,
David Miller <davem@...emloft.net>, aglo@...i.umich.edu,
shemminger@...tta.com, netdev@...r.kernel.org, rees@...ch.edu,
bfields@...ldses.org
Subject: Re: setsockopt()
On Mon, 07 Jul 2008 23:29:31 -0700
Roland Dreier <rdreier@...co.com> wrote:
> Interesting... I'd not tried nuttcp before, and on my testbed, which is
> a very high-bandwidth, low-RTT network (IP-over-InfiniBand with DDR IB,
> so the network is capable of 16 Gbps, and the RTT is ~25 microseconds),
> the difference between autotuning and not for nuttcp is huge (testing
> with 2.6.26-rc8 plus some pending 2.6.27 patches that add checksum
> offload, LSO and LRO to the IP-over-IB driver):
>
> nuttcp -T30 -i1 ends up with:
>
> 14465.0625 MB / 30.01 sec = 4043.6073 Mbps 82 %TX 2 %RX
>
> while setting the window even to 128 KB with
> nuttcp -w128k -T30 -i1 ends up with:
>
> 36416.8125 MB / 30.00 sec = 10182.8137 Mbps 90 %TX 96 %RX
>
> so it's a factor of 2.5 with nuttcp. I've never seen other apps behave
> like that -- for example NPtcp (netpipe) only gets slower when
> explicitly setting the window size.
>
> Strange...
I suspect that the link is so fast that the window growth isn't happening
fast enough. With only a 30 second test, you probably barely made it
out of TCP slow start.
--
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