xen-ia64-devel
Re: [Xen-ia64-devel] vIOSAPIC and IRQs delivery
Le Jeudi 09 Mars 2006 18:45, Tian, Kevin a écrit :
> From: Tristan Gingold
>
> >Sent: 2006年3月9日 16:17
> >
> >> Expensive? Yes.
> >>
> >> There are only 255 irqs - minus some that the base kernel steals
> >> for cmc, mca, timer, perfmon, etc. So any large system with a
> >> few hundred i/o cards _must_ share irqs. There aren't enough
> >> for one each.
> >
> >I don't agree. You can have interrupt domains. See "Intel Itanium
> > Processor Family Interrupt Architecture Guide".
> >
> >Tristan.
>
> OK, interrupt domains are only one option provided together with other
> two: share level-triggered irq line, and share vector number with multiple
> RTEs. Term "You" here refers to vendors, instead of us software developers.
> Vendors can support interrupt domains by providing multiple IOSAPICs, or
> they may implement by sharing level-triggered irq line physically. From VMM
> point of view, it shouldn't assume interrupt domains as the only option,
> and has to cover all cases.
>
> To me, it's also likely to imagine a mixed style: multiple IOSAPICs
> provided by the platform with total irq lines less than number of interrupt
> sources. In that case, people may partition interrupt domains, but finally
> still with irq line sharing even within local domain if it's electronically
> wired together. :-)
I really think this is pure theory.
IRQ lines were shared when hardware was costly: IBM-PC of 1981.
It is also less performant (we have to check all drivers) and less sure: what
about badly written drivers or fault tolerance?
Now IOSAPIC are cheap. I don't know any ia64 vendor sharing IRQs on PCI bus.
Maybe I am wrong, but until now it is true.
Furthermore, PCI-e has no more IRQ lines. IRQ are now in-band messages (MSI).
Thus sharing IRQs is not the future too.
Tristan.
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- RE: [Xen-ia64-devel] vIOSAPIC and IRQs delivery, (continued)
RE: [Xen-ia64-devel] vIOSAPIC and IRQs delivery, Tian, Kevin
RE: [Xen-ia64-devel] vIOSAPIC and IRQs delivery, Tian, Kevin
- Re: [Xen-ia64-devel] vIOSAPIC and IRQs delivery,
Tristan Gingold <=
RE: [Xen-ia64-devel] vIOSAPIC and IRQs delivery, Tian, Kevin
RE: [Xen-ia64-devel] vIOSAPIC and IRQs delivery, Tian, Kevin
RE: [Xen-ia64-devel] vIOSAPIC and IRQs delivery, Magenheimer, Dan (HP Labs Fort Collins)
RE: [Xen-ia64-devel] vIOSAPIC and IRQs delivery, Tian, Kevin
RE: [Xen-ia64-devel] vIOSAPIC and IRQs delivery, Dong, Eddie
RE: [Xen-ia64-devel] vIOSAPIC and IRQs delivery, Dong, Eddie
RE: [Xen-ia64-devel] vIOSAPIC and IRQs delivery, Tian, Kevin
|
|
|