Date: Wed, 10 Aug 2005 15:13:50 -0600 From: Scott Long <scottl@samsco.org> To: John Baldwin <jhb@freebsd.org> Cc: frank@exit.com, Andre Oppermann <andre@freebsd.org>, freebsd-arch@freebsd.org Subject: Re: Special schedulers, one CPU only kernel, one only userland Message-ID: <42FA6E0E.4070205@samsco.org> In-Reply-To: <200508101638.27087.jhb@FreeBSD.org> References: <42F9ECF2.8080809@freebsd.org> <200508100911.50004.jhb@FreeBSD.org> <1123704605.54957.8.camel@realtime.exit.com> <200508101638.27087.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin wrote: > On Wednesday 10 August 2005 04:10 pm, Frank Mayhar wrote: > >>On Wed, 2005-08-10 at 09:11 -0400, John Baldwin wrote: >> >>>I think this is the model that BSD/OS employed >>>for SMP in its 4.x series before they did their version of SMPng. >> >>I didn't grunge around in the scheduler (much), but as far as I'm aware >>BSD/OS 4.x used the Big Giant Lock mechanism just as FreeBSD did, and >>for the same reason. > > > I believe that at some point during the 4.x series they added a scheduler lock > that covered just enough to allow threads that weren't asleep in the kernel > to be switched to without require the big giant lock and that it was a pretty > decent performance win over the earlier single BGL ala FreeBSD 4.x. > So when a syscall is made on an AP, does it get serviced on the same AP (assuming that the lock is available and no sleeping is needed), or does it get serviced my the BSP? Where kernel threads explicitely pinned to the BSP? Was the APIC explicitely programmed to deliver only to the BSP? Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42FA6E0E.4070205>