From: Marc Leeman <marc.leeman@barco.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: eepro100 load
Date: Tue, 8 Jun 2004 16:15:23 +0200 [thread overview]
Message-ID: <20040608141523.GB9955@smtp.barco.com> (raw)
In-Reply-To: <20040608070108.GO18676@smtp.barco.com>
--ghzN8eJ9Qlbqn3iT
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
> 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).
The same goes for the e100 driver from Intel (haven't looked at the
non-default settings very much though); perhaps slightly worse as the
eepro100 driver, though the e100 driver seems to be able to limit limit
the resulting errors (overflow) to one source, while the eepro100 driver
distributes the errors over the different network sources, making them
all corrupt.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-06-08 14:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 7:01 eepro100 load Marc Leeman
2004-06-08 14:15 ` Marc Leeman [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=20040608141523.GB9955@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).