From: Ofer Fryman <ofer@shunra.co.il>
To: "'Bart Trojanowski'" <bart@jukie.net>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'linux-net@vger.kernel.org'" <linux-net@vger.kernel.org>
Subject: RE: network cards (drivers) performance.
Date: Tue, 10 Apr 2001 17:49:10 +0200 [thread overview]
Message-ID: <F1629832DE36D411858F00C04F24847A11DF8C@SALVADOR> (raw)
At what frame size?.
Thanks
Ofer
-----Original Message-----
From: Bart Trojanowski [mailto:bart@jukie.net]
Sent: Tuesday, April 10, 2001 4:30 PM
To: Ofer Fryman
Cc: 'linux-kernel@vger.kernel.org'; 'linux-net@vger.kernel.org'
Subject: Re: network cards (drivers) performance.
On Tue, 10 Apr 2001, Ofer Fryman wrote:
> Has any one tested the performance of the Tulip or AMD cards (or any other
> network card) on any Linux version, with any CPU and any chip-set?
Wow... that's a pretty broad question!
Yes I have had very good performance with the 'recent' tulip cards:
# lspci | grep DECchip
04:08.0 Ethernet controller: Digital Equipment Corporation DECchip 21142/43
(rev 41)
04:09.0 Ethernet controller: Digital Equipment Corporation DECchip 21142/43
(rev 41)
I have been able to tunnel about 186 Mbits/s on a P3Xeon/866 on any
2.4.{1,3}
kernel with two of the above cards (tulip driver). Note that this means
full duplex was on and the box was forwarding a total of 186 MBits of data
fron one NIC to another; actually it was 93 in each direction. Fast
routing (a la CONFIG_NET_FASTROUTE) was _not_ compiled into the kernel.
B.
--
WebSig: http://www.jukie.net/~bart/sig/
next reply other threads:[~2001-04-10 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-10 15:49 Ofer Fryman [this message]
2001-04-10 14:46 ` Bart Trojanowski
-- strict thread matches above, loose matches on Subject: below --
2001-04-10 15:16 Ofer Fryman
2001-04-10 14:29 ` Bart Trojanowski
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=F1629832DE36D411858F00C04F24847A11DF8C@SALVADOR \
--to=ofer@shunra.co.il \
--cc=bart@jukie.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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®