From: Thomas Mischke <thomas.mischke@isg.de>
To: linux-kernel@vger.kernel.org
Subject: Tulip and Interrupt mitigation
Date: Tue, 31 Jul 2001 14:22:48 +0200 [thread overview]
Message-ID: <3B66A318.1E530A35@isg.de> (raw)
Hello,
the tulip driver (as of 2.4.7, maybe earlyer versions too) has code in
tulip_interrupt to switch to interrupt mitigation on heavy network load.
The problem is: I have heavy network load, my system (Athlon 900 MHz
with 1 GB) spends 100% of the time in the interrupt, but it does not
switch to mitigation.
If I force the card to mitigation (by changing the code of tulip driver)
I don't loose any packets and get 20% idle time. Great!
I don't use CONFIG_NET_HW_FLOWCONTROL because sometimes my network goes
down for about 5 seconds. This does not happen without
CONFIG_NET_HW_FLOWCONTROL.
The problem seems to be the following: Mitigation is switched on if we
receive (or send) a lot of packets during a single interrupt. But this
never happens. During an interrupt I receive or send about 5 packets, so
no mitigation is started. But the interrupt is called very quickly after
leaving again, seeing another 5 packets and so on.
My tulip cards use 21143 chips.
Thanks in advance,
Thomas Mischke
reply other threads:[~2001-07-31 12:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3B66A318.1E530A35@isg.de \
--to=thomas.mischke@isg.de \
--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