From owner-freebsd-hackers@FreeBSD.ORG Fri May 23 22:20:48 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 F30F437B401 for ; Fri, 23 May 2003 22:20:47 -0700 (PDT) Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84FEA43F85 for ; Fri, 23 May 2003 22:20:47 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-38ldvet.dialup.mindspring.com ([209.86.253.221] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19JRSS-00035Y-00; Fri, 23 May 2003 22:20:40 -0700 Message-ID: <3ECF00E1.10A428AB@mindspring.com> Date: Fri, 23 May 2003 22:19:29 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Julian Elischer References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4edaf3d14038aeb454eecd142f02cd75e2601a10902912494350badd9bab72f9c350badd9bab72f9c cc: freebsd-hackers@freebsd.org cc: Dan Nelson cc: Daniel Eischen 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 05:20:48 -0000 Julian Elischer 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). > > 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. That's what I said. 8-). -- Terry