From: Benjamin LaHaise <bcrl@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Martin Josefsson <gandalf@wlug.westbo.se>,
Samium Gromoff <_deepfire@mail.ru>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.12-ac4 10Mbit NE2k interrupt load kills p166
Date: Thu, 25 Oct 2001 16:52:04 -0400 [thread overview]
Message-ID: <20011025165204.K23000@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0110252234270.27907-100000@tux.rsn.bth.se> <E15wrWY-0006EJ-00@the-village.bc.nu>
In-Reply-To: <E15wrWY-0006EJ-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Thu, Oct 25, 2001 at 09:54:46PM +0100
On Thu, Oct 25, 2001 at 09:54:46PM +0100, Alan Cox wrote:
> A faster machine will take as long as a slow machine with an ne2000. It
> doesn't matter if its an 8Mb 386 or a dual athlon, it will spend almost all
> of its ne2000 handling time poking bytes across an 8MHz bus.
Put another way: if you want a kernel that's optimised for 386es, use 2.0.
-ben
next prev parent reply other threads:[~2001-10-25 20:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-25 19:30 2.4.12-ac4 10Mbit NE2k interrupt load kills p166 Samium Gromoff
2001-10-25 20:01 ` Benjamin LaHaise
2001-10-25 20:22 ` Alan Cox
2001-10-25 20:40 ` Martin Josefsson
2001-10-25 20:54 ` Alan Cox
2001-10-25 20:52 ` Benjamin LaHaise [this message]
2001-12-08 21:58 ` Samium Gromoff
2001-12-10 10:54 ` vda
2001-10-27 15:22 ` Jussi Laako
2001-10-27 15:50 ` Samium Gromoff
2001-10-25 20:21 ` Alan Cox
2001-10-25 21:19 ` Urban Widmark
2001-10-26 2:57 ` Samium Gromoff
[not found] <Pine.LNX.4.33.0112091619190.6428-100000@coffee.psychology.mcmaster.ca>
2001-12-09 21:50 ` Samium Gromoff
2001-12-09 22:18 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-12-09 23:04 Samium Gromoff
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=20011025165204.K23000@redhat.com \
--to=bcrl@redhat.com \
--cc=_deepfire@mail.ru \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gandalf@wlug.westbo.se \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.