From: Marc Leeman <marc.leeman@gmail.com>
To: Linux PowerPC Embedded Mailinglist <linuxppc-embedded@ozlabs.org>
Subject: throughput question
Date: Tue, 28 Sep 2004 15:33:16 +0200 [thread overview]
Message-ID: <1f729c4804092806332aaf052e@mail.gmail.com> (raw)
I see some mails passing over the list about gigabit interfaces, so I
wonder if there are any suggestions as to what processor/interface
should be used for high througput.
I am currently working on a 8245 based board with 2.4.27 e100 driver
and when taking in (and processing streams), only about 50 Mbps can be
handled: about half of the time is based in kernel space (handling
interrupts).
The eepro100 driver was much worse.
As a result, I am a bit wondering about the higher bitrates. How much
do you achieve on tests with what hardware?
--=20
ash nazg durbatul=FBk, ash nazg gimbatul,
ash nazg thrakatul=FBk agh burzum-ishi krimpatul
next reply other threads:[~2004-09-28 13:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 13:33 Marc Leeman [this message]
2004-09-28 13:50 ` throughput question Matt Porter
-- strict thread matches above, loose matches on Subject: below --
2004-09-28 13:50 Fillod Stephane
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=1f729c4804092806332aaf052e@mail.gmail.com \
--to=marc.leeman@gmail.com \
--cc=linuxppc-embedded@ozlabs.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).