From: Marc Leeman <marc.leeman@barco.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: eepro100 load
Date: Tue, 8 Jun 2004 09:01:08 +0200 [thread overview]
Message-ID: <20040608070108.GO18676@smtp.barco.com> (raw)
A (quick) question:
we're using 82551ER silicon with the eepro100 driver to take in data.
After doing some tests where we tried to eliminate all^Wmost other
resource consuming factors, we came to the conclusion that a lot of the
used processing is done in kernel mode handling incoming data, which
seems to contradict the rumoured efficiency of the hardware/driver.
We are currently looking into some settings (rx buffers) in /proc, but
70-80 Mbps with a 350 MHz should be able to handle this without this
much load (seems to be > 60% in kernel mode for the moment for 56 Mbps).
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-06-08 7:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 7:01 Marc Leeman [this message]
2004-06-08 14:15 ` eepro100 load Marc Leeman
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=20040608070108.GO18676@smtp.barco.com \
--to=marc.leeman@barco.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).