From: Aaron Lehmann <aaronl@vitelus.com>
To: Rene Rebe <rene.rebe@gmx.net>
Cc: linux-kernel@vger.kernel.org, hfhsu@sis.com.tw, lcchang@sis.com.tw
Subject: Re: Disappointing SiS900 performance - driver issue?
Date: Thu, 13 Dec 2001 10:52:53 -0800 [thread overview]
Message-ID: <20011213105253.A14819@vitelus.com> (raw)
In-Reply-To: <20011213102423.B13809@vitelus.com> <20011213194555.50d6adeb.rene.rebe@gmx.net>
In-Reply-To: <20011213194555.50d6adeb.rene.rebe@gmx.net>
Hrm.
I get similar results.
On Thu, Dec 13, 2001 at 07:45:55PM +0100, Rene Rebe wrote:
> TCP/IP connection established.
> Packet size 1 k bytes: 10259 k bytes/sec
> Packet size 2 k bytes: 10146 k bytes/sec
> Packet size 4 k bytes: 10288 k bytes/sec
> Packet size 8 k bytes: 10317 k bytes/sec
> Packet size 16 k bytes: 10248 k bytes/sec
> Packet size 32 k bytes: 10173 k bytes/sec
[aaronl@endquote:~]$ ./netio 192.168.2.1
NETIO - Network Throughput Benchmark, Version 1.13
(C) 1997-2001 Kai Uwe Rommel
TCP/IP connection established.
Packet size 1 k bytes: 10102 k bytes/sec
Packet size 2 k bytes: 9460 k bytes/sec
Packet size 4 k bytes: 10129 k bytes/sec
Packet size 8 k bytes: 9912 k bytes/sec
Packet size 16 k bytes: 10112 k bytes/sec
Packet size 32 k bytes: 9773 k bytes/sec
But it doesn't live up to this on HTTP or FTP.
10:52:03 (3.64 MB/s) - `/dev/null' saved [4663650/4663650]
10:52:13 (4.19 MB/s) - `/dev/null' saved [4663650/4663650]
10:52:16 (3.99 MB/s) - `/dev/null' saved [4663650/4663650]
next prev parent reply other threads:[~2001-12-13 18:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-13 18:24 Disappointing SiS900 performance - driver issue? Aaron Lehmann
2001-12-13 18:41 ` Padraig Brady
2001-12-13 18:45 ` Rene Rebe
2001-12-13 18:52 ` Aaron Lehmann [this message]
[not found] ` <009a01c18441$144a7850$80d113ac@sis2234>
2001-12-14 13:52 ` Padraig Brady
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=20011213105253.A14819@vitelus.com \
--to=aaronl@vitelus.com \
--cc=hfhsu@sis.com.tw \
--cc=lcchang@sis.com.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=rene.rebe@gmx.net \
/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