All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
	xen-devel@lists.sourceforge.net, ian.pratt@cl.cam.ac.uk
Subject: Re: Interrupt forwarding
Date: Sat, 12 Mar 2005 15:07:17 -0500	[thread overview]
Message-ID: <9e47339105031212076030c603@mail.gmail.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3607@liverpoolst.ad.cl.cam.ac.uk>

On Sat, 12 Mar 2005 19:59:15 -0000, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:
> 
> 
> > > We don't go that far. A sensible approach would be to require the
> > > driver to be restarted, and to reset the hardware device, before
> > > unmasking. Or to rate limit each interrupt line to an
> > > administrator-configurable 'reasonable' number of IRQs per second --
> > > this might also catch bugs where drivers are not properly acking
> > > devices for other reasons.
> >
> > In x86 boxes almost everything is shared. Leaving the interrupt masked
> > off will probably disable 20% of the hardware in the box.
> 
> That's not my experience, certainly on modern server hardware. On
> systems with an IOAPIC its rare to see a shared interrupt, and even if
> you do you can typically avoid it just by swapping a couple of PCI cards
> around.
> 
> Ian
> 

If I load video drivers two more drivers will share interrupts. 169
with have 4 devices on it instead of three.

[jonsmirl@jonsmirl proc]$ cat interrupts
           CPU0       CPU1
  0:     484259     448188    IO-APIC-edge  timer
  8:          0          0    IO-APIC-edge  rtc
  9:          0          0   IO-APIC-level  acpi
 14:        776        762    IO-APIC-edge  ide0
 15:       8040       7726    IO-APIC-edge  ide1
169:      37509          0   IO-APIC-level  libata, uhci_hcd:usb4, eth0
185:          5          0   IO-APIC-level  ehci_hcd:usb1
193:        548        272   IO-APIC-level  uhci_hcd:usb2, uhci_hcd:usb5
201:          0          0   IO-APIC-level  uhci_hcd:usb3
209:          3          0   IO-APIC-level  ohci1394
NMI:          0          0
LOC:     932357     932306
ERR:          0
MIS:          0
[jonsmirl@jonsmirl proc]$

-- 
Jon Smirl
jonsmirl@gmail.com


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-03-12 20:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-12 19:59 Interrupt forwarding Ian Pratt
2005-03-12 20:07 ` Jon Smirl [this message]
2005-03-13 10:01   ` Keir Fraser
2005-03-13 15:56     ` Jon Smirl
2005-03-13 16:01       ` Keir Fraser
2005-03-13 16:49         ` Jon Smirl
  -- strict thread matches above, loose matches on Subject: below --
2005-03-12 18:11 Ian Pratt
2005-03-12 18:21 ` Keir Fraser
2005-03-12 18:33   ` Jon Smirl
2005-03-12 18:48     ` Keir Fraser
2005-03-12 18:53       ` Jon Smirl
2005-03-12 18:59       ` Jon Smirl
2005-03-12 18:02 Jon Smirl
2005-03-12 18:12 ` Mark Williamson
2005-03-14 15:39   ` Ronald G. Minnich
2005-03-14 15:44     ` Mark Williamson
2005-03-14 16:01       ` Ronald G. Minnich
2005-03-14 16:04         ` Ronald G. Minnich
2005-03-14 21:59       ` Andi Kleen

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=9e47339105031212076030c603@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=ian.pratt@cl.cam.ac.uk \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=xen-devel@lists.sourceforge.net \
    /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.