From: Jon Mason <jdmason@us.ibm.com>
To: Rick Jones <rick.jones2@hp.com>
Cc: netdev@oss.sgi.com
Subject: Re: on the wire behaviour of TSO on/off is supposed to be the same yes?
Date: Fri, 21 Jan 2005 13:58:53 -0600 [thread overview]
Message-ID: <200501211358.53783.jdmason@us.ibm.com> (raw)
In-Reply-To: <41F1516D.5010101@hp.com>
The benefit of TSO is not throughput, but CPU utilization. Throughput
increase is usually a side effect because of better PCI DMA behavior (eg.
large PCI transfers are better). Are you seeing a CPU utilization decrease?
On Friday 21 January 2005 01:01 pm, Rick Jones wrote:
> Is it indeed supposed to be the case that the on the wire behaviour of TCP with
> TSO on/off is supposed to be the same? I'm seeing some cases (netperf
> TCP_STREAM 2.6.10 sending to HP-UX 11.23) where the throughput differences are
> >= 10 MB/s on an e1000 card (TSO being slower). I've got lots of netperf and
> tcpdump but thought I'd ask first before dumping it onto the list. Actually,
> i'll probably have to put it up on the net somewhere since it is O(200MB) in
> total (although I have a smaller point example).
>
> sincerely,
>
> rick jones
>
>
>
--
Jon Mason
jdmason@us.ibm.com
next prev parent reply other threads:[~2005-01-21 19:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 19:01 on the wire behaviour of TSO on/off is supposed to be the same yes? Rick Jones
2005-01-21 19:58 ` Jon Mason [this message]
2005-01-21 20:18 ` Rick Jones
2005-01-21 20:44 ` David S. Miller
2005-01-21 22:00 ` Rick Jones
2005-01-21 22:18 ` David S. Miller
2005-01-21 22:48 ` Rick Jones
2005-01-21 22:58 ` Rick Jones
2005-01-22 4:44 ` David S. Miller
2005-01-22 18:58 ` rick jones
2005-01-22 4:49 ` David S. Miller
2005-01-22 19:05 ` rick jones
2005-01-24 20:33 ` Rick Jones
2005-01-24 20:43 ` David S. Miller
2005-01-24 21:22 ` Rick Jones
2005-01-28 0:10 ` Rick Jones
2005-01-28 0:57 ` David S. Miller
2005-01-28 1:36 ` Rick Jones
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=200501211358.53783.jdmason@us.ibm.com \
--to=jdmason@us.ibm.com \
--cc=netdev@oss.sgi.com \
--cc=rick.jones2@hp.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).