From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Bill Fink <billfink@mindspring.com>
Cc: Anton Blanchard <anton@samba.org>,
<linuxppc-dev@lists.linuxppc.org>,
"David S. Miller" <davem@redhat.com>
Subject: Re: GigE Performance Comparison of GMAC and SUNGEM Drivers
Date: Mon, 19 Nov 2001 13:54:59 +0100 [thread overview]
Message-ID: <20011119125459.20923@smtp.adsl.oleane.com> (raw)
In-Reply-To: <20011119111548.F4531@krispykreme>
>
>
>Hi,
>
>> The GMAC driver had significantly better performance. It sustained
>> 663 Mbps for the 60 second test period, and used 63 % of the CPU on
>> the transmitter and 64 % of the CPU on the receiver. By comparison,
>> the SUNGEM driver only achieved 588 Mbps, and utilized 100 % of the
>> CPU on the transmitter and 86 % of the CPU on the receiver. Thus,
>> the SUNGEM driver had an 11.3 % lower network performance while
>> using 58.7 % more CPU (and was in fact totally CPU saturated).
This is weird and unexpected as GMAC will request interrupt for each
transmitted packet while sungem won't
However, I noticed that sungem is getting a lot of rxmac and txmac
interrupts, I'll investigate this a bit more.
(Could you check the difference of /proc/interrupts between a test
with gmac and a test with sungem ?)
Note that I just updated sungem in my rsync tree, it now has all of
the power management and ethtool/miitool support.
I plan to replace gmac with sungem completely, so it would be nice to
figure out where that problem comes from.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-19 12:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-18 6:45 GigE Performance Comparison of GMAC and SUNGEM Drivers Bill Fink
2001-11-19 0:15 ` Anton Blanchard
2001-11-19 12:54 ` Benjamin Herrenschmidt [this message]
2001-11-20 6:34 ` Bill Fink
2001-11-20 12:02 ` Benjamin Herrenschmidt
2001-11-20 19:50 ` David S. Miller
2001-11-21 0:05 ` benh
2001-11-21 0:19 ` David S. Miller
2001-11-21 1:25 ` Benjamin Herrenschmidt
2001-11-21 4:17 ` Bill Fink
2001-11-21 3:46 ` Bill Fink
2001-11-21 5:36 ` Anton Blanchard
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=20011119125459.20923@smtp.adsl.oleane.com \
--to=benh@kernel.crashing.org \
--cc=anton@samba.org \
--cc=billfink@mindspring.com \
--cc=davem@redhat.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).