From: Malcolm Beattie <mbeattie@sable.ox.ac.uk>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [UPDATE] Fresh zerocopy patch on kernel.org
Date: Wed, 31 Jan 2001 15:26:54 +0000 [thread overview]
Message-ID: <20010131152653.C13345@sable.ox.ac.uk> (raw)
In-Reply-To: <14966.35438.429963.405587@pizda.ninka.net>
In-Reply-To: <14966.35438.429963.405587@pizda.ninka.net>; from davem@redhat.com on Tue, Jan 30, 2001 at 01:33:34AM -0800
David S. Miller writes:
>
> At the usual place:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/davem/zerocopy-2.4.1-1.diff.gz
Hmm, disappointing results here; maybe I've missed something.
Setup is a Pentium II 350MHz (tusk) connected to a Pentium III
733MHz (heffalump) (both 512MB RAM) with SX fibre, each with a
3Com 3C985 NIC. Kernels compared are 2.4.1 and 2.4.1+zc
(the 2.4.1-1 diff above) using acenic driver with MTU set to 9000.
Sysctls set are
# Raise socket buffer limits
net.core.rmem_max = 262144
net.core.wmem_max = 262144
# Increase TCP write memory
net.ipv4.tcp_wmem = 100000 100000 100000
on both sides.
Comparison tests done were
gensink4: 10485760 (10MB) buffer size, 262144 (256K) socket buffer
ftp: server does sendfile() from a 300MB file in page cache,
client does read from socket/write to /dev/null in 4K chunks.
2.4.1 2.4.1+zc
KByte/s tusk%CPU heff%CPU KByte/s tusk%CPU heff%CPU
gensink4
tusk->heffalump 94000 58-100 93 54000 98-102 11-45
heffalump->tusk 72000 86-100 46-59 70000 71-93 53-71
2.4.1 2.4.1+zc
KByte/s KByte/s
ftp heffalump->tusk 86000 62000
I was impressed with the raw 2.4.1 figures and hoped to be even more
impressed with the 2.4.1+zc numbers. Is there something I'm missing or
can change or do to help to improve matters or track down potential
problems?
--Malcolm
--
Malcolm Beattie <mbeattie@sable.ox.ac.uk>
Unix Systems Programmer
Oxford University Computing Services
-
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-31 15:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-30 9:33 [UPDATE] Fresh zerocopy patch on kernel.org David S. Miller
2001-01-30 11:16 ` Chris Wedgwood
2001-01-30 12:23 ` David S. Miller
2001-01-30 18:59 ` Tom Rini
2001-01-31 15:26 ` Malcolm Beattie [this message]
2001-02-01 1:51 ` David S. Miller
2001-02-01 11:20 ` Malcolm Beattie
2001-02-01 11:25 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2001-01-30 15:58 Pau Aliagas
2001-02-01 8:20 ` Chris Wedgwood
2001-02-01 16:06 Jonathan Earle
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=20010131152653.C13345@sable.ox.ac.uk \
--to=mbeattie@sable.ox.ac.uk \
--cc=davem@redhat.com \
--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