All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gunther Mayer <gunther.mayer@gmx.net>
To: Zwane Mwaikambo <zwane@mwaikambo.name>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] per isr in_progress markers
Date: Tue, 10 Sep 2002 20:07:22 +0200	[thread overview]
Message-ID: <3D7E34DA.7010100@gmx.net> (raw)
In-Reply-To: Pine.LNX.4.44.0209092120310.1096-100000@linux-box.realnet.co.sz

Zwane Mwaikambo wrote:

>On Mon, 9 Sep 2002, Linus Torvalds wrote:
>
>  
>
>>I agree with you, but that is only true for edge-triggered APIC
>>interrupts, though - for level-triggered ones we will just re-take the
>>interrupt when we unmask it again.
>>
>>Which is kind of sad. Is there some fast way to read the status of a 
>>level-trigger irq off the IO-APIC in case it is still pending, and to do 
>>the mitigation even for level-triggered?
>>    
>>
>
>perhaps Remote IRR might help there?
>
>  
>
>>(Btw, if there is, that would also allow us to notice the "constantly
>>screaming PCI interrupt" without help from the low-level isrs)
>>    
>>
>
>As an aside, i just had an idea for another way to improve interrupt 
>handling latency. Instead of walking through all the isrs in the chain, 
>we can have an isr flag wether it was the source of the irq, and if so we 
>stop right there and not walk through the other isrs. 
>
This method is flawed for edge-triggered interrupts: you will miss any
interrupts which come in before you acked the first.



  parent reply	other threads:[~2002-09-10 18:00 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 [this message]
2002-09-10 18:38                       ` Zwane Mwaikambo
2002-09-10  7:46                   ` Rogier Wolff
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=3D7E34DA.7010100@gmx.net \
    --to=gunther.mayer@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.