From: Daniel Freedman <freedman@ccmr.cornell.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: TCP performance eepro100
Date: Thu, 6 Dec 2001 23:12:25 -0500 [thread overview]
Message-ID: <20011206231225.A32585@ccmr.cornell.edu> (raw)
In-Reply-To: <054401c17ed2$3b03a0d0$0f00a8c0@minniemouse>
In-Reply-To: <054401c17ed2$3b03a0d0$0f00a8c0@minniemouse>; from marsaro@interearth.com on Thu, Dec 06, 2001 at 07:49:53PM -0800
On Thu, Dec 06, 2001, Jon wrote:
> Has anyone done testing on eepro100 and seen really poor performance? I am
> seeing that the eepro100 in SuSE 2.4.7 and above is 50% slower than than
> 2.4.2 in RH 7.1 I am doing a simple test with ttcp against another RH server
> and then SuSE vs SuSE or vs the RH system. In all cases the eepro100at best
> shows 39mbs. In modules.conf I am setting options="0x30" that forces 100mbps
> Full Duplex, this is also reflected in dmesg. With the new intel e100 it is
> possible to get 60mbps on SuSE. Is there something in the Kernel build or
> Driver build that is multi-casting or filtering that may cause this? Any
> ideas at this point would help. BTW, I am using SMP Kernels on all the
> systems.
Jon,
No great thoughts other than to report that I did netpipe-tcp (from
Debian woody) testing of my eepro100's using a custom SMP 2.4.9
kernel, and easily saw 90 megabits per second. Sorry I couldn't help
more.
Take care,
Daniel
> Regards,
>
> Jon
>
--
Daniel A. Freedman
Laboratory for Atomic and Solid State Physics
Department of Physics
Cornell University
prev parent reply other threads:[~2001-12-07 4:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 3:49 Jon
2001-12-07 4:12 ` Daniel Freedman [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=20011206231225.A32585@ccmr.cornell.edu \
--to=freedman@ccmr.cornell.edu \
--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
all inboxes | Powered by JetHome®