netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: lm@bitmover.com (Larry McVoy)
To: Rick Jones <rick.jones2@hp.com>
Cc: Larry McVoy <lm@bitmover.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	davem@davemloft.net, wscott@bitmover.com, netdev@vger.kernel.org
Subject: Re: tcp bw in 2.6
Date: Tue, 2 Oct 2007 10:20:02 -0700	[thread overview]
Message-ID: <20071002172002.GO17418@bitmover.com> (raw)
In-Reply-To: <47027C63.803@hp.com>

On Tue, Oct 02, 2007 at 10:14:11AM -0700, Rick Jones wrote:
> Larry McVoy wrote:
> >A short summary is "can someone please post a test program that sources
> >and sinks data at the wire speed?"  because apparently I'm too old and
> >clueless to write such a thing.
> 
> WRT the different speeds in each direction talking with HP-UX, perhaps 
> there is an interaction between the Linux TCP stack (TSO perhaps) and 
> HP-UX's ACK avoidance heuristics. If that is the case, tweaking 
> tcp_deferred_ack_max with ndd on the HP-UX system might yield different 
> results.

I doubt it because I see the same sort of behaviour when I have a group
of Linux clients talking to the server.  The HP box is in the mix
simply because it has a gigabit card and that makes driving the load
simpler.  But if I do several loads from 100Mbit clients I get the same
packet throughput.

> WRT the small program making a setsockopt(SO_*BUF) call going slower than 
> the rsh, does rsh make the setsockopt() call, or does it bend itself to the 
> will of the linux stack's autotuning?  What happens if your small program 
> does not make setsockopt(SO_*BUF) calls?

I haven't tracked down if rsh does that but I've tried doing it with 
values of default, 64K, 1MB, and 10MB with no difference.

> *) depending on the quantity of CPU around, and the type of test one is 

These are fast CPUs and they are running at 93% idle while running the test.
-- 
---
Larry McVoy                lm at bitmover.com           http://www.bitkeeper.com

  reply	other threads:[~2007-10-02 17:20 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070929142517.EC6AB5FB21@work.bitmover.com>
     [not found] ` <alpine.LFD.0.999.0709290914410.3579@woody.linux-foundation.org>
     [not found]   ` <20070929172639.GB7037@bitmover.com>
     [not found]     ` <alpine.LFD.0.999.0709291050200.3579@woody.linux-foundation.org>
2007-10-02  0:59       ` tcp bw in 2.6 Larry McVoy
2007-10-02  2:14         ` Linus Torvalds
2007-10-02  2:20           ` Larry McVoy
2007-10-02  3:50             ` David Miller
2007-10-02  4:23               ` Larry McVoy
2007-10-02 15:06             ` John Heffner
2007-10-02 17:14             ` Rick Jones
2007-10-02 17:20               ` Larry McVoy [this message]
2007-10-02 18:01                 ` Rick Jones
2007-10-02 18:40                   ` Larry McVoy
2007-10-02 19:47                     ` Rick Jones
2007-10-02 21:32                     ` David Miller
2007-10-03  7:19               ` Bill Fink
2007-10-02 10:52         ` Herbert Xu
2007-10-02 15:09           ` Larry McVoy
2007-10-02 15:41             ` Larry McVoy
2007-10-02 16:25               ` Larry McVoy
2007-10-02 16:47                 ` Stephen Hemminger
2007-10-02 16:49                   ` Larry McVoy
2007-10-02 17:10                     ` Stephen Hemminger
2007-10-15 12:40                   ` Daniel Schaffrath
2007-10-15 15:49                     ` Stephen Hemminger
2007-10-02 16:34               ` Linus Torvalds
2007-10-02 16:48                 ` Larry McVoy
2007-10-02 21:16                   ` David Miller
2007-10-02 21:26                     ` Larry McVoy
2007-10-02 21:47                       ` David Miller
2007-10-02 22:17                         ` Rick Jones
2007-10-02 22:32                           ` David Miller
2007-10-02 22:36                             ` Larry McVoy
2007-10-02 22:59                               ` Rick Jones
2007-10-03  8:02                               ` David Miller
2007-10-02 16:48               ` Ben Greear
2007-10-02 17:11                 ` Larry McVoy
2007-10-02 17:18                   ` Ben Greear
2007-10-02 17:21                     ` Larry McVoy
2007-10-02 17:54                       ` Stephen Hemminger
2007-10-02 18:35                         ` Larry McVoy
2007-10-02 18:29             ` John Heffner
2007-10-02 19:07               ` Larry McVoy
2007-10-02 19:29                 ` Linus Torvalds
2007-10-02 20:31                   ` David Miller
2007-10-02 19:33                 ` Larry McVoy
2007-10-02 19:53                   ` John Heffner
2007-10-02 20:14                     ` Larry McVoy
2007-10-02 20:40                       ` Rick Jones
2007-10-02 20:42                       ` Wayne Scott
2007-10-02 21:56                         ` Linus Torvalds
2007-10-02 19:27             ` Linus Torvalds
2007-10-02 19:53               ` Rick Jones
2007-10-02 20:33               ` David Miller
2007-10-02 20:44                 ` Roland Dreier
2007-10-02 21:21                 ` Larry McVoy
2007-10-03 21:13                   ` Pekka Pietikainen
2007-10-03 21:23                     ` Larry McVoy
2007-10-03 21:50                       ` Pekka Pietikainen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071002172002.GO17418@bitmover.com \
    --to=lm@bitmover.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=rick.jones2@hp.com \
    --cc=torvalds@linux-foundation.org \
    --cc=wscott@bitmover.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).