From: David Mosberger <davidm@napali.hpl.hp.com>
To: "Feldman, Scott" <scott.feldman@intel.com>
Cc: davidm@hpl.hp.com, linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [patch] e1000 TSO parameter
Date: Mon, 14 Jul 2003 22:31:00 -0700 [thread overview]
Message-ID: <16147.37268.946613.965075@napali.hpl.hp.com> (raw)
In-Reply-To: <20030714214510.17e02a9f.davem@redhat.com>
[Scott, somehow I never received your original response so I'm
replying based on what I saw in the linux.kernel newgroup...]
Scott> Do you have any data to share?
Sure, I don't see why not. Here are the number I got:
TSO disabled:
$ modprobe InterruptThrottleRate=0,0,0,0 TSO=0,0,0,0
$ netperf -l 30 -c -C -H foobar -- -s64K -S64K
TCP STREAM TEST to foobar
Recv Send Send Utilization Service Demand
Socket Socket Message Elapsed Send Recv Send Recv
Size Size Size Time Throughput local remote local remote
bytes bytes bytes secs. 10^6bits/s % S % S us/KB us/KB
131070 131072 131072 30.00 897.16 34.07 35.00 3.111 3.196
TSO enabled:
$ modprobe InterruptThrottleRate=0,0,0,0 TSO=1,1,1,1
$ netperf -l 30 -c -C -H foobar -- -s64K -S64K
TCP STREAM TEST to foobar
Recv Send Send Utilization Service Demand
Socket Socket Message Elapsed Send Recv Send Recv
Size Size Size Time Throughput local remote local remote
bytes bytes bytes secs. 10^6bits/s % S % S us/KB us/KB
131070 131072 131072 30.00 894.09 11.65 34.48 1.068 3.159
This looks roughly like you'd expect: with TSO, slightly lower
throughput but much less CPU overhead.
With ftp, things get stranger: fetching a 2GByte file via ftp get
(from the remote end):
TSO disabled:
ftp> get big.iso /dev/null
local: /dev/null remote: big.iso
200 PORT command successful.
150 Opening BINARY mode data connection for 'big.iso' (2038628352 bytes).
226 Transfer complete.
2038628352 bytes received in 18.17 secs (109554.5 kB/s)
ftp server CPU utilization: ~ 40%
With TSO enabled:
ftp> get big.iso /dev/null
local: /dev/null remote: big.iso
200 PORT command successful.
150 Opening BINARY mode data connection for 'big.iso' (2038628352 bytes).
226 Transfer complete.
2038628352 bytes received in 21.16 secs (94070.2 kB/s)
ftp server CPU utilization: ~ 15%
So we get almost 15% of throughput drop. This was with plain "netkit
fptd". AFAIK, it does a simple read/write loop (not sendfile()).
--david
next prev parent reply other threads:[~2003-07-15 5:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 4:42 Feldman, Scott
2003-07-15 4:45 ` David S. Miller
2003-07-15 4:57 ` David Mosberger
2003-07-15 5:31 ` David Mosberger [this message]
2003-07-15 5:38 ` David S. Miller
2003-07-15 23:01 ` David Mosberger
2003-07-16 1:39 ` David S. Miller
2003-07-16 6:32 ` David Mosberger
2003-07-16 6:30 ` David S. Miller
2003-07-29 6:53 ` Anton Blanchard
2003-07-15 5:11 Feldman, Scott
2003-07-16 0:27 Feldman, Scott
2003-07-16 0:41 ` David Mosberger
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=16147.37268.946613.965075@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=davidm@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=scott.feldman@intel.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
all inboxes | Powered by JetHome®