From: Anders Peter Fugmann <afu@fugmann.dhs.org>
To: Jerome Tollet <Jerome.Tollet@qosmos.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel 2.4.2 network performances
Date: Thu, 22 Mar 2001 18:29:52 +0100 [thread overview]
Message-ID: <3ABA3690.8040708@fugmann.dhs.org> (raw)
In-Reply-To: <3AB08FAC.657784CA@qosmos.net> <3AB9366E.3060905@fugmann.dhs.org> <3AB9C083.C093769F@qosmos.net>
Hi again.
I've written my own test program, and I get 12M throughput.
I used a packet size of 1024 Bytes. Smaller packages seems to result in
less throughput.
There was no load on the machine I tested on. Does the throughput get
better is there is a lot of stress on the machine? (eg. compiling kernel
with -j 10).
It could also be the NIC itself, but this I cannot test (I'm using a
3Com 905b) card. Have you tried to replace the NIC?
--
Hi. I'm a .signature virus.
Please copy me into your .signature file and help me spread.
prev parent reply other threads:[~2001-03-22 17:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-15 9:47 kernel 2.4.2 network performances Jerome Tollet
2001-03-15 13:42 ` Sampsa Ranta
2001-03-16 9:33 ` Helge Hafting
2001-03-16 23:24 ` Bernd Eckenfels
2001-03-16 23:54 ` bert hubert
2001-03-21 23:17 ` Anders Peter Fugmann
[not found] ` <3AB9C083.C093769F@qosmos.net>
2001-03-22 17:29 ` Anders Peter Fugmann [this message]
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=3ABA3690.8040708@fugmann.dhs.org \
--to=afu@fugmann.dhs.org \
--cc=Jerome.Tollet@qosmos.net \
--cc=linux-kernel@vger.kernel.org \
/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