From owner-freebsd-hackers@FreeBSD.ORG Fri May 23 23:35:43 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA30D37B401 for ; Fri, 23 May 2003 23:35:43 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23C0043FBF for ; Fri, 23 May 2003 23:35:43 -0700 (PDT) (envelope-from eischen@pcnet1.pcnet.com) Received: from pcnet1.pcnet.com (localhost [127.0.0.1]) by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h4O6ZWwQ016077; Sat, 24 May 2003 02:35:32 -0400 (EDT) Received: from localhost (eischen@localhost)h4O6ZVfH016073; Sat, 24 May 2003 02:35:31 -0400 (EDT) Date: Sat, 24 May 2003 02:35:31 -0400 (EDT) From: Daniel Eischen To: Terry Lambert In-Reply-To: <3ECF01BE.BF58609A@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org cc: Dan Nelson cc: Julian Elischer Subject: Re: libkse and SMP (was Re: USB bulk read & pthreads) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 May 2003 06:35:44 -0000 On Fri, 23 May 2003, Terry Lambert wrote: > Daniel Eischen wrote: > > On Fri, 23 May 2003, Terry Lambert 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). > > > > If I am reading you correctly, then no. Scope process > > threads will block in the kernel, but upcalls will be > > made to the originating KSE and new threads will be > > scheduled. > > I'm rereading it, but I don't see that interpretation. > > I guess if both you and Julian both called me on it, I must > have misexpressed myself, but I currently don't understand > how. 8-|. I think it was the part about "a single CPU system with PTHREAD_SCOPE_PROCESS (the default) can still get itself blocked in the kernel by a single blocking call" without mentioning that it won't block other scope process threads from being run. -- Dan Eischen