From: Jeff Garzik <jgarzik@pobox.com>
To: Daniel Egger <degger@fhm.edu>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Netdev <netdev@oss.sgi.com>
Subject: Re: [NET] net driver updates
Date: Tue, 13 Apr 2004 14:31:16 -0400 [thread overview]
Message-ID: <407C31F4.9070800@pobox.com> (raw)
In-Reply-To: <FE87A41F-8809-11D8-8F2A-000A9597297C@fhm.edu>
Daniel Egger wrote:
> On 06.04.2004, at 17:30, Jeff Garzik wrote:
>
>> * Francois work on r8169, epic100, sis190: PCI DMA, NAPI, other minor
>> fixes and cleanups
>
>
> r8169 seems to work though it is not even a tad bit faster
> than plain 2.6.5.
Francois is still trying to fix all the vendor-created bugs, so
performance is a secondary consideration.
RTL8169 is a nice chipset, though. Robert Ollsson had some nice pktgen
numbers for it, IIRC.
> Those cards are really driving me nuts. Between two r8169 cards, one
> on Athlon with kernel 2.4.24, one on Athlon with 2.6.5 or 2.4.24, I
> get 90Mbit/s in one direction and 39Mbit/s in the other using iperf and
> TCP. With iperf and UDP they deliver 100Mbit/s resp. 230Mbit/s depending
> on the direction. Crosschecking with my PowerBook (OS X) shows that I can
> get 844Mbit/s (UDP) or 572Mbit/s (TCP) to one host and 844Mbit/s (UDP) but
> only 88Mbit/s (TCP) to the other.
>
> The environment is switched and changing cables and/or ports doesn't
> improve the results.
>
> Ideas? (Yeah, I'll get Intel NICs RSN...)
Yeah -- I plan to kill r8169, and use 8139cp.c to drive it instead :)
Jeff
next prev parent reply other threads:[~2004-04-13 18:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-06 15:30 [NET] net driver updates Jeff Garzik
2004-04-06 20:35 ` Daniel Egger
2004-04-13 18:31 ` Jeff Garzik [this message]
2004-04-13 19:54 ` Francois Romieu
2004-04-13 21:09 ` Daniel Egger
2004-04-14 10:13 ` Francois Romieu
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=407C31F4.9070800@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=degger@fhm.edu \
--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;
as well as URLs for NNTP newsgroup(s).