public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Zwane Mwaikambo <zwane@mwaikambo.name>,
	Ingo Molnar <mingo@elte.hu>, Robert Love <rml@tech9.net>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RFC] per isr in_progress markers
Date: Sun, 08 Sep 2002 19:03:28 -0400	[thread overview]
Message-ID: <3D7BD740.8080906@mandrakesoft.com> (raw)
In-Reply-To: Pine.LNX.4.44.0209081453010.1293-100000@home.transmeta.com

Linus Torvalds wrote:
> On Sun, 8 Sep 2002, Zwane Mwaikambo wrote:
> 
>>Here is a newer (untested) patch incorporating Ingo's suggestions as well 
>>as adding an extra request_irq flag so that isrs can use isr_unmask_irq() 
>>to enable their interrupt lines.
> 
> 
> Hmm.. I really don't get the point of what this is supposed to actually 
> help.
> 
> Clearly, if the device doesn't share the irq line, this doesn't matter. 
> Similarly, it shouldn't matter if there is just one device that is active 
> (ie irq line sharing with some slow device where the interrupt happens 
> fairly seldom).
> 
> As far as I can tell, the only time when this might be an advantage is an 
> SMP machine with multiple devices sharing an extremely busy irq line. Then 
> the per-isr in-progress bit allows multiple CPU's to actively handle 
> several of the devices at the same time.


IMO one should seek to avoid sharing an IRQ line at all.  I dunno that 
you really want to tune for that case, when the user could vastly 
improve the situation by manipulating IRQs in BIOS setup or similar 
IRQ-distribution methods.

On an SMP box you especially want to distribute irqs to take best 
advantage of irq affinity.

	Jeff



  reply	other threads:[~2002-09-08 22:59 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 [this message]
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
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=3D7BD740.8080906@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --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