From: Andrew Morton <andrewm@uow.edu.au>
To: jamal <hadi@cyberus.ca>
Cc: lkml <linux-kernel@vger.kernel.org>,
"netdev@oss.sgi.com" <netdev@oss.sgi.com>
Subject: Re: sendfile+zerocopy: fairly sexy (nothing to do with ECN)
Date: Mon, 29 Jan 2001 03:05:16 +1100 [thread overview]
Message-ID: <3A74433C.239D1317@uow.edu.au> (raw)
In-Reply-To: <3A72CD1E.32BB523F@uow.edu.au> <Pine.GSO.4.30.0101270900230.24088-100000@shell.cyberus.ca>
jamal wrote:
>
> PS:- can you try it out with the ttcp testcode i posted?
Yup. See below. The numbers are almost the same as
with `zcs' and `zcc'.
The CPU utilisation code which was in `zcc' has been
broken out into a standalone tool, so the new `cyclesoak'
app is a general-purpose system load measurement tool.
It's fascinating to play with, if you're into that sort
of thing.
`cyclesoak' was used to measure ttcp-sf and NFS/UDP client
and server throughput. The times()-based instrumentation
inside ttcp-sf doesn't (can't) give correct numbers. 2-4% CPU
at 100 mbps? We wish :)
The zerocopy patch doesn't seem to affect NFS efficiency at
all. Confused.
Excerpt from the rapidly swelling README:
NFS/UDP client results
======================
Reading a 100 meg file across 100baseT. The file is fully cached on
the server. The client is the above machine. You need to unmount the
server between runs to avoid client-side caching.
The server is mounted with various rsize and wsize options.
Kernel rsize wsize mbyte/sec CPU
2.4.1-pre10+zc 1024 1024 2.4 10.3%
2.4.1-pre10+zc 2048 2048 3.7 11.4%
2.4.1-pre10+zc 4096 4096 10.1 29.0%
2.4.1-pre10+zc 8199 8192 11.9 28.2%
2.4.1-pre10+zc 16384 16384 11.9 28.2%
2.4.1-pre10 1024 1024 2.4 9.7%
2.4.1-pre10 2048 2048 3.7 11.8%
2.4.1-pre10 4096 4096 10.7 33.6%
2.4.1-pre10 8199 8192 11.9 29.5%
2.4.1-pre10 16384 16384 11.9 29.2%
Small diff at 8192.
NFS/UDP server results
======================
Reading a 100 meg file across 100baseT. The file is fully cached on
the server. The server is the above machine.
Kernel rsize wsize mbyte/sec CPU
2.4.1-pre10+zc 1024 1024 2.6 19.1%
2.4.1-pre10+zc 2048 2048 3.9 18.8%
2.4.1-pre10+zc 4096 4096 10.0 34.5%
2.4.1-pre10+zc 8199 8192 11.8 28.9%
2.4.1-pre10+zc 16384 16384 11.8 29.0%
2.4.1-pre10 1024 1024 2.6 18.5%
2.4.1-pre10 2048 2048 3.9 18.6%
2.4.1-pre10 4096 4096 10.9 33.8%
2.4.1-pre10 8199 8192 11.8 29.0%
2.4.1-pre10 16384 16384 11.8 29.0%
No diff.
ttcp-sf Results
===============
Jamal Hadi Salim has taught ttcp to use sendfile. See
http://www.cyberus.ca/~hadi/ttcp-sf.tar.gz
Using the same machine as above, and the following commands:
Sender: ./ttcp-sf -t -c -l 32768 -v receiver_host
Receiver: ./ttcp-sf -c -r -l 32768 -v sender_host
CPU
2.4.1-pre10-zerocopy, sending with ttcp-sf: 10.5%
2.4.1-pre10-zerocopy, receiving with ttcp-sf: 16.1%
2.4.1-pre10-vanilla, sending with ttcp-sf: 18.5%
2.4.1-pre10-vanilla, receiving with ttcp-sf: 16.0%
-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-28 15:58 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-27 5:45 Andrew Morton
2001-01-27 6:20 ` Aaron Lehmann
2001-01-27 8:19 ` Andrew Morton
2001-01-27 10:09 ` Ion Badulescu
2001-01-27 10:45 ` Andrew Morton
2001-01-30 6:00 ` David S. Miller
2001-01-30 12:44 ` Andrew Morton
2001-01-30 12:52 ` David S. Miller
2001-01-30 14:58 ` Andrew Morton
2001-01-30 17:49 ` Chris Wedgwood
2001-01-30 22:17 ` David S. Miller
2001-01-31 0:31 ` Chris Wedgwood
2001-01-31 0:45 ` David S. Miller
2001-01-30 22:28 ` David S. Miller
2001-01-30 23:34 ` Andrew Morton
2001-02-02 10:12 ` Andrew Morton
2001-02-02 12:14 ` Trond Myklebust
2001-02-02 17:51 ` David Lang
2001-02-02 22:46 ` David S. Miller
2001-02-02 22:57 ` David Lang
2001-02-03 2:27 ` James Sutherland
2001-02-02 23:09 ` David S. Miller
2001-02-02 23:13 ` David Lang
2001-02-02 23:28 ` Jeff Barrow
2001-02-02 23:31 ` David S. Miller
2001-01-27 10:05 ` Ion Badulescu
2001-01-27 10:39 ` Andrew Morton
2001-01-27 12:49 ` jamal
2001-01-30 1:06 ` Ion Badulescu
2001-01-30 2:48 ` jamal
2001-01-30 3:26 ` Ion Badulescu
2001-01-31 0:53 ` Still not sexy! (Re: " jamal
2001-01-31 0:59 ` Ingo Molnar
2001-01-31 1:04 ` jamal
2001-01-31 1:14 ` Ingo Molnar
2001-01-31 1:39 ` jamal
2001-01-31 11:21 ` Malcolm Beattie
2001-01-31 11:24 ` Ingo Molnar
2001-01-31 1:10 ` Still not sexy! (Re: sendfile+zerocopy: fairly sexy (nothing to dowith ECN) Rick Jones
2001-01-31 1:45 ` jamal
2001-01-31 2:25 ` Still not sexy! (Re: sendfile+zerocopy: fairly sexy (nothing todowith ECN) Rick Jones
2001-02-04 19:48 ` jamal
2001-02-05 18:51 ` Rick Jones
2001-02-05 5:13 ` David S. Miller
2001-01-27 12:43 ` sendfile+zerocopy: fairly sexy (nothing to do with ECN) jamal
2001-01-27 13:29 ` Andrew Morton
2001-01-27 14:15 ` jamal
2001-01-28 16:05 ` Andrew Morton [this message]
2001-01-29 18:50 ` Rick Jones
[not found] ` <200101271854.VAA02845@ms2.inr.ac.ru>
2001-01-28 5:34 ` Andrew Morton
2001-01-28 13:37 ` Felix von Leitner
2001-01-28 14:11 ` Dan Hollis
2001-01-28 14:27 ` Andi Kleen
2001-01-29 21:50 ` Pavel Machek
2001-01-28 19:43 ` Gregory Maxwell
2001-01-28 19:48 ` Choosing Linux NICs (was: Re: sendfile+zerocopy: fairly sexy (nothing to do with ECN)) Felix von Leitner
2001-01-29 16:16 sendfile+zerocopy: fairly sexy (nothing to do with ECN) Jonathan Earle
2001-01-29 16:34 ` Antonin Kral
2001-01-31 1:49 Bernd Eckenfels
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=3A74433C.239D1317@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=hadi@cyberus.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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®