From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Zwane Mwaikambo <zwane@mwaikambo.name>,
Robert Love <rml@tech9.net>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RFC] per isr in_progress markers
Date: Tue, 10 Sep 2002 09:46:16 +0200 [thread overview]
Message-ID: <20020910094616.B21776@bitwizard.nl> (raw)
In-Reply-To: <Pine.LNX.4.33.0209091151200.14841-100000@penguin.transmeta.com>
On Mon, Sep 09, 2002 at 11:53:40AM -0700, Linus Torvalds wrote:
>
> (Btw, if there is, that would also allow us to notice the "constantly
> screaming PCI interrupt" without help from the low-level isrs)
OH! That'd be nice: instead of a lockup if a PCI device's interrupt
isn't serviced, you get a nice message and a machine that might
still work!
On the other hand, you have a possibility for disaster if the
threshold isn't set right.
I have written serial drivers where the card will limit the interrupt
rate to max 100 per second. I then build in a detection: if my IRQ
handler gets called more than 10 times in a jiffy, we're in trouble.
Turns out that I left this in "in the field" and some people put the
serial card on the same interrupt line as a SCSI controller. The
scsi controller can generate more than 1000 interrupts per second ->
my driver shuts down....
Something similar may happen if say you net-spray a sligtly
under-powered machine with a Gigabit ethernet card: The GBE card may
indeed have a new packet ready by the time the interrupt tries to
return. Leads to an interesting DOS: just send a bunch of packets
in quick succession and the machine drops off the internet...
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* The Worlds Ecosystem is a stable system. Stable systems may experience *
* excursions from the stable situation. We are currenly in such an *
* excursion: The stable situation does not include humans. ***************
next prev parent reply other threads:[~2002-09-10 7:41 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-07 22:34 [PATCH][RFC] per isr in_progress markers Zwane Mwaikambo
2002-09-08 7:55 ` Ingo Molnar
2002-09-08 8:15 ` Ingo Molnar
2002-09-08 10:38 ` Zwane Mwaikambo
2002-09-08 13:31 ` Zwane Mwaikambo
2002-09-08 16:59 ` Zwane Mwaikambo
2002-09-08 22:01 ` Linus Torvalds
2002-09-08 23:03 ` Jeff Garzik
2002-09-09 6:49 ` bert hubert
2002-09-09 16:24 ` Linus Torvalds
2002-09-09 10:06 ` Ingo Molnar
2002-09-09 15:06 ` Linus Torvalds
2002-09-09 18:44 ` Ingo Molnar
2002-09-09 18:53 ` Linus Torvalds
2002-09-09 19:37 ` Zwane Mwaikambo
2002-09-09 19:23 ` Ingo Molnar
2002-09-09 20:05 ` Zwane Mwaikambo
2002-09-09 20:08 ` Andrew Morton
2002-09-10 15:05 ` David Woodhouse
2002-09-10 15:32 ` Alan Cox
2002-09-10 22:37 ` Gérard Roudier
2002-09-09 19:38 ` Maciej W. Rozycki
2002-09-10 11:55 ` Stephan von Krawczynski
2002-09-10 18:07 ` Gunther Mayer
2002-09-10 18:38 ` Zwane Mwaikambo
2002-09-10 7:46 ` Rogier Wolff [this message]
2002-09-08 10:57 ` Zwane Mwaikambo
2002-09-09 20:40 ` Alan Cox
2002-09-09 20:48 ` Andre Hedrick
2002-09-10 17:47 ` Zwane Mwaikambo
-- strict thread matches above, loose matches on Subject: below --
2002-09-09 9:49 zwane
2002-09-09 14:34 ` Robert Love
2002-09-09 18:23 ` Zwane Mwaikambo
2002-09-09 10:13 zwane
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=20020910094616.B21776@bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rml@tech9.net \
--cc=torvalds@transmeta.com \
--cc=zwane@mwaikambo.name \
/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