Date: Wed, 22 Jun 2005 15:54:37 +0200 From: Emanuel Strobl <Emanuel.strobl@gmx.net> To: freebsd-current@freebsd.org Cc: Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= <des@des.no> Subject: Re: lapic@2k interrukts eating CPU cycles Message-ID: <200506221554.41750@harrymail> In-Reply-To: <86slza27md.fsf@xps.des.no> References: <200506091423.39940@harrymail> <200506220122.24315@harrymail> <86slza27md.fsf@xps.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart3712098.U1lv971hoi Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Mittwoch, 22. Juni 2005 09:06 schrieb Dag-Erling Sm=F8rgrav: > Emanuel Strobl <Emanuel.strobl@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=20 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, =2DHarry > > DES --nextPart3712098.U1lv971hoi Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBCuW2hBylq0S4AzzwRAsP0AJ9YC9B6N/nCKRGqmGZ66vBUWR+BxwCZASy4 kU2jxyhxmXLWVfcyCRZQP68= =pKxi -----END PGP SIGNATURE----- --nextPart3712098.U1lv971hoi--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200506221554.41750>