lapic@2k interrukts eating CPU cycles

[John Baldwin]

On Wednesday 22 June 2005 09:54 am, Emanuel Strobl wrote:
> Am Mittwoch, 22. Juni 2005 09:06 schrieb Dag-Erling Smørgrav:
> > Emanuel Strobl <Emanuel.strobl at gmx.net> writes:
> > > I don't know what lapic stands for (the l, if apic means
> > > AdvancedProgrammableInterruptController)
> >
> > local, meaning per-CPU as opposed to the IOAPIC which is located in
> > the south bridge and shared by all CPUs.
>
> Hmm, why do I see a lapic on my UP system? I've never seen before I
> upgraded to -current (short before the code freeze to help finding bugs)
> And what does the "ti" mean? ( from systat "2030 lapic0: ti" )
>
> Thanks a lot,

Every CPU since at least the PPro (and SMP-capable Pentiums) has had a local 
APIC.  Using the APIC system instead of AT PIC allows PCI interrupts to not 
be shared in most cases which is a good thing. :)  The 'ti' is short for 
timer because systat chops of the names.  If you do 'vmstat -i' you will see 
the full name.

-- 
John Baldwin <jhb at FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org