Re: next-20081030: voyager compile busted

[Ingo Molnar]

* H. Peter Anvin <hpa@xxxxxxxxx> wrote:

> James Bottomley wrote:
> > 
> > Yes ... been having IRC conversations about that.  We'd need to use
> > runtime patching to fix the performance regressions virtualisation has
> > been causing us first ... but then we could use it for voyager.
> 
> I thought we already were, at least to some degree (the call sites 
> are way too big and way bigger than they need to be, so we end up 
> with a lot of NOPs.  I proposed a solution to Jeremy at Kernel 
> Summit, but he basically said "I don't want to maintain that, I 
> don't care about hardware performance", which is understandable but 
> highly unfortunate.)

in practice the function pointer overhead is almost unmeasurable for 
things like IPIs which are rather expensive to issue. In fact it's 
probably more expensive on Voyager as it does not utilize the local 
APIC for SMP messaging (which is pretty much the only 
performance-sensitive thing here). It uses its own glue logic it 
appears, which is almost certainly behind the system bus.

James, how many cycles do typical SMP ops take on Voyager?

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/