Date: Fri, 23 May 2003 16:33:07 -0400 (EDT) From: Daniel Eischen <eischen@pcnet1.pcnet.com> To: Julian Elischer <julian@elischer.org> Cc: Dan Nelson <dnelson@allantgroup.com> Subject: Re: libkse and SMP (was Re: USB bulk read & pthreads) Message-ID: <Pine.GSO.4.10.10305231627160.8151-100000@pcnet1.pcnet.com> In-Reply-To: <Pine.BSF.4.21.0305231113460.92012-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 23 May 2003, Julian Elischer wrote: > > > On Fri, 23 May 2003, Terry Lambert wrote: > > > Daniel Eischen wrote: > > > > This is handy to know; so basically, my expectation from > > reading the code around PTHREAD_SCOPE_SYSTEM was correct: > > a single CPU system with PTHREAD_SCOPE_PROCESS (the default) > > can still get itself blocked in the kernel by a single > > blocking call (as in the USB bulk read device issue). > > > No you are completely wrong.. > > Each PTHREAD_SCOPE_PROCESS gets its OWN KSE to run on. > that thread may block but other threads may run unimpeded. I'm not sure if what you meant here, but here's a (hopefully) clearer explanation. All threads that are created with PTHREAD_SCOPE_PROCESS (the default) will run in the same (initial) KSEG. The initial KSEG will have as many KSEs as CPUs by default. When a scope process thread blocks in the kernel, upcalls are made to the originating KSE and a new thread is scheduled. When scope process threads unblock in the kernel, upcalls are made to one or more of the same KSEs within the initial KSEG to notify the library that the threads can be resumed. Each scope system thread gets its own KSE/KSEG pair in which to run. -- Dan Eischen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10305231627160.8151-100000>