From: Chuck Ebbert <76306.1226@compuserve.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.x high irq contention
Date: Tue, 22 Apr 2003 14:44:48 -0400 [thread overview]
Message-ID: <200304221448_MC3-1-3589-7226@compuserve.com> (raw)
>> Won't help a lot. If its all IRQ load (eg lots of multicast streaming
>> audio small frames) then you want an eepro100 or something similar that
>> has interrupt mitigators.
>
> Well, handwaving about the network load/type ;-)
> Could as well be two RTL back-to-back, normal packets but high bandwidth.
> (watch collisions for this case :-)
RTL-8139: the hardware equivalent of a bicycle.
8))
------
Chuck
next reply other threads:[~2003-04-22 18:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 18:44 Chuck Ebbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-22 10:12 2.4.x high irq contention Chuck Ebbert
2003-04-22 3:32 Anton Petrusevich
2003-04-22 10:40 ` Stephan von Krawczynski
2003-04-22 13:47 ` Alan Cox
2003-04-22 17:50 ` Stephan von Krawczynski
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=200304221448_MC3-1-3589-7226@compuserve.com \
--to=76306.1226@compuserve.com \
--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 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).