[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Re: [PATCH 0/4] pci: interrupt status/interrupt disable

From: Michael S. Tsirkin
Subject: Re: [Qemu-devel] Re: [PATCH 0/4] pci: interrupt status/interrupt disable support
Date: Thu, 26 Nov 2009 14:59:10 +0200
User-agent: Mutt/1.5.19 (2009-01-05)

On Thu, Nov 26, 2009 at 12:41:03PM +0000, Paul Brook wrote:
> > No, this would slow us down because these are per-pin.
> > We need a sum of interrupts so that config space
> > can be updated by a single command.
> > Interrupts are a fastpath, extra loops there should be avoided.
> It's really not that much of a fast path. Unless you're doing something 
> particularly obscure then even under heavy load you're unlikely to exceed a 
> few kHz.

I think with kvm, heavy disk stressing benchmark can get higher.

> Compared to the average PIC implementation, and the overhead of the 
> actual CPU interrupt, I find it hard to believe that looping over precisely 4 
> entries has any real performance hit.
> Paul

I don't think it is major, but I definitely have seen, in the past,
that extra branches and memory accesses have small but measureable effect
when taken in interrupt handler routines in drivers, and same should
apply here.

OTOH keeping the sum around is trivial.

It might not be easily measureable now, but IMO that's just because the
whole interrupt delivery is so complex. E.g.  we currently have there a
loop re-computing interrupt routing on each access, this is just silly
and I intend to fix it.  I would rather not introduce more code that
will have to be cleaned up later.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]